Our build history hasn't updated in 4 days even there there are several builds per day (https://travis-ci.org/mitodl/lore/builds). It starting to become a problem for our release processes. Does anyone know how we can get it fixed?
It turns out we had disabled push based builds in our settings, and re-enabling those started adding builds to the build-history tab.
Related
To test something on Jenkins I changed the date to 3 days in the future. After I did the testing I set the date back to today but it seems that this causes some troubles.
Automated builds were running while I was testing so Jenkins already generated some builds/logs in the future. I think this might be causing problems now. When running a new build the green balls aren't flashing anymore and it looks like it is building but I don't see any console outputs in the logs on today.
Anyone also experienced this problem? How can I solve this? Maybe the deleting the logs in the future could help I think but how do you do this correctly?
I solved this issue by deleting the build history of all my jobs. %HUDSON_HOME%\jobs\ directory and delete all the subdirectories (only the directories, not config.xml!!) there as described in How do I clear my Jenkins/Hudson build history? .
I'm having some trouble preventing a Scheduled Build from being automatically kicked off after the same build has been trigger manually and no changes are present.
Problem: The Build is scheduled to go out at 3am everyday but only if any changes have been made (the Settings option ‘Build even if nothing has changed since the previous build’ is Unchecked). The problem is that if you trigger a manual build and no changes are made afterwards, the Scheduled Build is still going to get triggered even if there are no changes. Please follow the scenario bellow for an example:
Scenario:
Scheduled build gets kicked off today at 3am - assembly version changes to 1.0.0.1
On the same day, several changes are checked-in before noon.
The same Build is kicked off manually at 1pm - assembly version changes to 1.0.0.2
No more check-ins are made after the manual build from 1pm
The next day at 3am the Scheduled build gets triggered which it shouldn't have (assembly version changes to 1.0.0.3) since there were no check-ins since 1pm (triggered manually).
It seems like the 1pm build is not even being considered and accounted for.
It looks like TFS is taking in count check-ins since the last “Scheduled Build” rather than “the last completed Build” (same build definition) which in this case was the manually triggered one.
So my question is: “Is there any way we can prevent TFS from triggering Scheduled build if there were no check-ins after a manual build has been kicked off?”
Currently, it looks like TFS does not have that option anywhere in the Build Definition
Thank you in advance
In order to do this you would need to write your own scheduler that checked the previous manual build for you. You could write a TfsJob for this or even as a a scheduled powershell that runs at the allotted time...
I ran into this issue today as well.
It seems this is currently "by design".
Someone else posted a suggestion to "fix" this here:
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/5702884--build-even-if-nothing-has-changed-since-the-previ
Is there a plugin to jenkins(hudson) that can visually show all jobs and there runs in future as well as in the past.
ex: if Job A is scheduled to run once every day at 8 AM. The plugin should show the previous run of the job as well as scheduled runs in the future.
I searched in Jenkins Plugins Link and found Google Calendar but there are two things different about this plugin
It is linked to job status hence I am presuming it will only show previous runs
It needs an online calendar account.
No, you would have to write such a plugin.
"Next executions" plugin helpful a bit:
https://wiki.jenkins-ci.org/display/JENKINS/Next+Executions
The plug-in calendar-view is doing what you are looking for.
Features as of version Version: 0.3.1:
Features
Provides a month, week and day view of past and future builds
Indicates status of past builds by color
Displays when future scheduled builds will happen
Shows estimated duration of future scheduled builds
Configurable date and time settings
Environment: TFS 2010
I met a strange issue on the TFS 2010.
I create a rolling build, and set it should be triggered no more often than every 30 minutes.
Usually, it works fine. I can find the build was triggered several times one day.
Then there is a long vacation and after I came back, the rolling build was not triggered in the last two days.
There is nothing changed for the build definition and TFS server.
It is very strange.
Does anyone know the reason or have the same situation?
BTW, I have a little question for rolling builds. That is, Rolling builds work when there are accumulate check-ins until the prior build finishes. If 1:00 AM, a rolling build was triggered, it will finish at 1:20. At 1:10 some new code was checked in, an other build such as nightly build was triggered before 1:20. Question: Is the rolling build triggered at 1:30?
The whole point of rolling builds is so they don't build up in a queue, basically it means if anyone checks in while a build is happening it won't trigger a build.
If you set a time, eg 30 minutes, it won't ever build within 30 minutes of a previous build.
For the next build to happen you need to check in again outside of those conditions (eg 30 minutes later)
I checked in some code and my build was added to the build queue. I can't go home until the build passes.
There is nobody in front of me, but it's been well over half an hour since my checkin and my build hasn't started (plus it's a half an hour to build the 49 large projects against the build environment). I've been at work since morning and just want to go home before midnight (it's past 8:30 already). My checkin's just sitting their in queue, not being fired off.
How do I force the build to start in an empty build machine if there is nobody in front of me in queue and nothing else going on?
edit: This is what I get for breaking my own rule of never checking in after 3pm unless it's a mandate.
Open the Team Explorer pane and navigate to your team project. Expand the 'Builds' node and find the build definition that you need to build. You should then be able to right-click it an choose 'Queue new build..'. (This does require a separate permission, and you may not have that permission).
This will then bring up the confirmation dialog where you can specify the shelveset to build (if its a gated build).
If the Builds screen shows that there are queued builds, and none running - it could be that there are no available Build Agents or they are marked offline. See Manage Your Build System for more information about how to check the status of your build agents.