I have successfully setup a CCNet web dashboard and everything is working fine has expected.
And i have triggered a force build from CCNET and it ran successfully with out causing any error. but, the problem what i am facing is that, whenever i'm triggering the build from CCNET dashboard (Force) it's keeps on to build continuously again and again.
Actually it should stop the build automatically right after the success of the latest build.
can any one help me out, how to stop the continuous builds ????
Thanks in Advance !!!
Indeed, check your triggers.
See "Next Build Time" column on the dashboard. If it has date/time then project has a trigger. If not - you'll see "Force Build Only".
Check your build's triggers. You've probably got it set to force a build at a very frequent interval.
Related
In build history I'm seeing a new button saying stop streaming builds, what does it mean in google cloud build
Google seems to be pushing a new UI.
Monday I was getting it every so often, yesterday I got it all day.
The "Stop Streaming" stops the page from auto updating.
The old UI, had a "refresh" button as new builds would not show automatically
I've tried it with a few test examples and it seems like the only thing it does is stop showing you the creation of new builds in the UI, until you refresh the page.
Hope you guys can help me with this weird issue I'm facing.
The app bundle is getting build everything time it finishes building. So its like once it gets to 100% it starts all over again. One thing I made to kind of solve it, is to enable the "Remote debugging" option on the expo App. But that will only work for a minute and will start the loop of building the bundle again.
I have also reinstalled the node_modules & cleaned expo cache but nothing seems to be working.
Ok, I found it. It was because of iCloud Drive on MAC. For some reason that I don't understand (since it did not happen before under the same conditions) the refresh of the files is forced.
So move your app folder to another place that is not on iCloud Drive and it will work.
Hope this will help.
It was Dropbox sync causing my issue.
Most of the time you shouldn’t need to rebuild your APK on every change, you should only need to run exp publish to see your updated app show up in your existing APK. If you change anything in app.json you’ll need to run the build again, but if you aren’t touching app.json then you should be mostly fine to just publish and not run a standalone build.
I have done a number of changes to a build configuration in TeamCity 8. I know I can see an audit trail of the changes that I have done to the build configuration and I can check the details of each individual change, but I wonder if I can select one of those previous versions of the build configuration and restore it; there doesn't seem to be any obvious option in TeamCity for this.
For the avoidance of doubt, I'm not after reverting changes in the source code, but in the build configuration of TeamCity. I changed a few parameters, build steps, triggers, etc., and I want to revert those changes.
You are right ,there is no obvious option in Teamcity to rollback to a previous version.
However, all teamcity build configurations are maintained in a xml file on the local disk drive in the Local Build Server. The files are created in a rolling format (the latest config is called config.xml, the one previous to it is config-1..xml). If you can figure out from the audit page on which exact xml you want to rollback to, you can copy the backed up config.xml to the recent one, or you can make the changes manually.
I would recommend playing with this on a test target first and then doing it on the original target.
As of TeamCity 2017, there is a link to a page with recent changes to a configuration:
Press 'view history' and you will end up on a page where there's a list of changes.
Press 'view change':
There you will see a "diff" comparison, identical to the one you have in git:
Sometimes it's hard to navigate, but you can surely see what was changed. This is especially useful for accidents when you deleted a piece of script, and saved the configuration. This can get your script back.
Hope it helps you after you after 8 years and 4 months!
Let's say I have one TeamCity build configuration depending on artifacts taken from another.
It is possible to publish artifacts while build is in progress in TeamCity.
My question is: is it possible to trigger build when all necessary artifacts are available even if builds that are providing these artifacts are still in progress?
The purpose of this is to speed up builds a little.
Thank you!
TeamCity, as far as I know, only has the option to trigger on finish of another build configuration, not after publishing artifacts which as you say you can do while the build is still in progress.
Let me ask you another question:
Since whatever you are doing in the build after the publication of the artifacts didn't of course stop you from publishing the artifacts, can't you extract that part out into another build configuration and then have that part fetch the artifacts from this one? This way you can make whatever build configuration you wanted to trigger as soon as you get the artifacts, trigger, well, as soon as you get the artifacts.
Is it possible to trigger a Hudson/Jenkins build only when a certain string appears in a commit-message?
For instance, I want to trigger a build that rolls out my application to the dev environment by writing a commit message like:
MYPROJECT-123 Fixed NPE in MyClass.java #deploy:DEV
The general idea is described in this great talk on Continuos Deployment but I couldn't find any information on how to do this in Hudson.
I would prefer to have this behavior in Hudson itself and not in an external system like commit-hooks or web-hooks.
I don't know of an out of the box way you can parse the SCM message as part of the trigger. You have a couple of options that might achieve what you want though
Write your own Hudson SCM plugin
Chain your jobs together into a build pipeline. The first job could simply look for that message in the changelog.xml to determine if the next build is triggered or not.
If you are looking at building a pipeline of build jobs, check out the build-pipeline-plugin. http://www.centrumsystems.com.au/blog/?p=121
Anyone got a more elegant solution??
Cheers,
Geoff
There is a plugin called Commit Message Trigger Plugin, but it had just a 0.1 release.
Maybe the easiest way is to use a version control post commit (or push) trigger to start a Hudson Job. You'd one anyway to automatically start your build.