I have upgraded Jenkins from 1.639 to 2.60 by replacing the WAR file on the windows server.
However following this, on the jenkins job view i no longer get the drop down menu for some of the jobs
In some cases I can get the drop down menu from the All jobs view but not another specific view tab. But in other cases the drop down menu does not appear on the All view or any other tab the job is on. In all cases this worked prior to upgrade.
This does not seem to be related to thee manage of old data or for how recent a job has been run.
Transpires it was a browser compatibility issue. I had been using Chrome 21 but when I swapped and used IE 11 the drop down menus were consistently available on the upgraded 2.60 versions
Related
I am an admin on our Jenkins master but, this button is not available for any builds for any user.
I found this question which has a somewhat relevant answer since we are also using Matrix-based security, however no one has this button showing up on any build
Is there a plugin required to have this feature available?
My version isJenkins ver. 2.105
Keep forever option appears only when relevant, meaning only if you opt in on other option Discard old builds. If not it's irrelevant see jenkins users answer
option only appears if you have chosen to Discard Builds
from the config for the job. (i.e. if you have chosen not to discard
any builds have a certain time/build number, then the button won't
show).
This question already has answers here:
Jenkins: remove old builds with command line
(12 answers)
Closed 7 years ago.
I removed old build folders from the build directory in Jenkins expecting them to be removed in the UI, unfortunately whilse these build directories are gone, their UI link still exists. I now have two questions:
How can I get rid of the defunct links in the UI?
How can I delete old build from cli and have it reflected in the UI?
A better way to remove old builds is discard-old-build plugin where you can specify how many builds you want to keep and all older builds are discarded.
You must either restart Jenkins or reload the data, in order to reconcile the UI with its back end. There is no other way.
If you have access to the "Manage Jenkins" menu there is a link to "Reload Configuration from Disk", which is a little less invasive than a restart.
Keep in mind that the system will be not usable for a few seconds while the data is reloaded, just like during a full restart. If you have a lot of builds, this might take a little. So, make sure that this is ok with the other users of your system.
The Completed Build section in our TFS 2013 installation only shows.. recent builds ..when clicking on a build definition.
Not even sure what criteria I would use but it seems everything older than a day is scrapped.
However, picking a particular build from the build definition or the little green-red-bar graph on the left (ok/failed builds) always displays the information.
So is there a way to configure the number of recent builds shown on the web page when selecting the build definition?
Having an empty list of builds there confused developers no too comfy with the TFS server and most don't bother clicking on the bar graph on the left to browse to a particular build.
is it not just a case of using the drop down in the top right of the screen to display longer time periods?
I'm using MS Project to manage my TFS work items. The standard Summary Task Information window that comes up when double-clicking on a task is slightly inadequate when dealing with TFS work items. It lacks the standard work item view that we're accustomed to within Visual Studio, and that MS has elegantly rendered within visualstudio.com.
I noticed today that if I set a task field to invalid value, then Work Item Publishing Errors window comes up and there's a nifty little button Edit Work Item... that displays the work item in the standard VS view. Now I'm searching all over Project to figure out how to edit a work item in this view without first having to cause a publishing error. There must be some button I've overlooked in Project that opens a TFS work item up in the VS-like view, isn't there?
It's currently not possible and its also not intended to be used that way. The UI in Ms Project is the native Project UI and is mant to receive the updates to the plan and to layout the items into a new plan.
Managing the contents of the items is all meant to be done from the Web UI. With the new Work Item UI you'll be redirected to the Web whenever you need to edit a work item. Visual Studio, Excel and Project won't show you a native editor window anymore.
You'll be able to directly to the work item editor on the web from the team tab. When connecting to older versions of TFS, this would open the Work Item editor:
I have a Team Foundation Server 2008 Installation and a separate machine with the Team Build service.
I can create team builds and trigger them manually in Visual Studio or via the command line (where they complete successfully). However check ins to the source tree do not cause a build to trigger despite the option to build every check in being ticked on the build definition. Update: To be clear I had a fully working build definition with the CI option enabled.
The source tree is configured is a pretty straight forward manner with code either under a Main folder or under a Branch\branchName folder. Each branch of code (including main) has a standard Team Build definition relating to the solution file contained within. The only thing that is slightly changed from default settings is that the build server working folder; i.e. for main this is Server:"$\main" Local:"c:\build\main" due to path length.
The only thing I've been able to guess at (possible red herring) is that there might be some oddity with the developer workspaces. Currently each developer maps Server:"$\" to local:"c:\tfs\" so that there is only one workspace for all branches. This is mainly to avoid re-mapping problems that some of the developers had previously gotten themselves into. But I can't see how this would affect CI.
UPDATE: Ifound the answer indirectly; please read below
Ok I have found the answer myself after several dead ends. In the end I fixed this unintentionally while fixing another issue. Basically we had just turned on the automatic execution of unit tests for our builds. The test would run sucessfully but then immediately the build would bomb out with a message saying it was unable to report to the build drop folder.
What was happening was that while the Build service runs under one account and has a set of rights; some of the functionality is actually driven through the TFSService account. fter wading a heap of permissions I had my tests being reported. Then I noticed that builds had started to trigger on check-ins; I can't tell you exactly which permission fixed this but hopefully this answer will at least set people down the right path.
One other note a few of the builds started failing due to conflicting workspace mappings - this was a separate issue that I resolved by deleting some obsolete workspaces using the Attrice Sidekicks for Team Foundation tool.
Hope this helps somebody else.
Select your team project from team explorer, then right click on the Builds folder. Select a new build definition and then select the trigger tab. Move the radio button to "Build each check-in (more builds)"
More info can be found here
MSDN How to: Create a Build Definition
Are there any errors in the log on the TFS application server? Anything that indicates that it tried to fire but failed?