Cruiscontrol sometimes can't connect to the repository and build fails. Is there a way that I can have cruisecontrol try to build again automatically when something like this happens????? In other words, I want cruisecontrol to keep building when it fails until build is successful...
Thanks
The Java version or .NET?
If the Java version use buildafterfailed=true.
Related
ALL,
I have a project on GitHub which is an application I'm still developing.
On Linux I'm using Anjuta as an IDE to generate the Makefile and build it.
The problem I'm facing is that I just build myself a newer machine with the newer set of autotools and now the project fails to build because its Makefile is set to use the older version.
In particular make complains about using aclocal version 1.15 and the newer box have aclocal version 1.16.
What would be the process of making the code build I presume I need to run some kind of reconfiguration tool to make the configure aware of the upgrade. I just don't know how and what.
Also, if someone can help on what files needs to be in the source control so that every single time I update everything will be regenerated automatically.
TIA!!
After build happens in Jenkins,Iam trying to do package of node.js application in jenkins
I think you will find the NodeJS Jenkins plugin provides the functionality you are describing.
In Visual Studio Online you can now set build dependencies on the General tab of a build definition.
But.. is there a way to set the version of Node.js and NPM?
It seems like a hosted build agent is currently using Node.js v0.12.7 and NPM v2.11.3 but I need Node.js v4.2+ and NPM v3.3+. Is there a way to enforce it?
P.S.: On-premise VSO build agent is not an option.
There is now a Node Tool installer available. The link to software inventory shared by Daniel was very helpful, and I discovered the installer digging into the Node specs for Hosted VS2017 agent.
Finds or downloads and caches the specified version of Node.js and adds it to the PATH
Try adding a Node Tool installer step before your node/npm steps.
It seems like there's a lot of misunderstanding as to what "demands" are. A build with a specific demand does not change what software is available on the build agent. A "demand" is simply a method of a build task expressing what requirements it has, so it can run on an agent that has the desired demands satisfied (these are the build agent's "capabilities").
This list of software is what's on the hosted build agent. If it's not there, and you can't install it via npm or the like, then you're out of luck.
Where could I acquire a working copy of compiled JavaFX app bundled with JRE so I could execute this app on ARM linux?
or
How can I create my JavaFX app + JRE bundle that would work on ARM Linux
Best case scenario for me would be to be ableto create copy-paste enabled folder tree or single executable file..
I do understand that this question might be too vague, but I desperately need some help on this. I have spent more than 6 evenings + 2 nights searching how to get a compiled JavaFX application ( .jar file) to run on ARM linux on UDOO (RPi2-like) board.
I have been more of an .NET guy a long time, and now I had to make WPF-like rich UX app that would run on this specific hardware, and I chose JavaFX due to its likeliness to WPF. It does run fine on my desktop PCs but I absolutely can not get it to run on ARM linux.
I am trying to do this too. Did you get it working? My solution is to package the JAR using tools provided by IntelliJ or any other IDE, include the JRE in a folder within the app, then write a script that invokes the JAR from the included JRE like:
lib/jre/bin/java -jar runthis.jar
I also tried it for two days now but didn't get it to work.
I use maven in combination with the javafx-maven-plugin to build native installers of an application.
At first I got the error, that the javafx-ant.jar tools are missing:
[ERROR] Failed to execute goal build-jar(create-jfxjar) on project foo:
Execution create-jfxjar of goal build-jar failed: Plugin javafx-maven-plugin or
one of its dependencies could not be resolved: Could not find artifact
javafx-packager:javafx-packager:jar:1.8.0 at specified path
/opt/jdk1.8.0/jre/../lib/ant-javafx.jar
Then I found the ant-javafx.jar in a windows JDK but then another error was reported that linux is not supported with this one. Ok so I downloaded a linux JDK and used that ant-javafx.jar. Now it could build and create a *.deb file successfully!
However when I started the installer it failed with a message and when checking the log (/var/log/apt/term.log)
Log started: 2021-04-29 00:40:01
dpkg: Error creating archive
/home/pi/Foo/target/jfx/native/foo.deb (--unpack):
package architecture (amd64) does not match system (armhf)
Then I did research and found the following mailing list entry:
[...] the Java Packager isn’t shipped with any ARM builds that I’m aware of. Currently it is only for X86 Windows, Linux and Mac. [...]
This basically explains it: The packager doesn't work on ARM for now. Maybe we should write the guy to encurage him to add it...
=> So for now I work with the jar directly.
I'm getting error - One or more Dlls have change stopping after cloning in git for 1 hour. We have been running cc.net with hg and now trying to migrate to git.
I'm getting this error , not sure how else to proceed.
this is due to the fact that the first integration with git will get all mods :-(
download the latest dev release, it has been fixed.
The 1.8.5 version of CCNet will be out soon.
http://build.nauck-it.de/download/CruiseControl.NET-dev/