Jenkins Docker workflow script for gcc cli and gui #768
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 |
endJunction
added a commit
that referenced
this pull request
Jul 17, 2015
Jenkins Docker workflow script for gcc cli and gui
|
OpenGeoSys development has been moved to GitLab. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to the Workflow-plugin Jenkins jobs can now be configured via scripts similar to Travis. This has the advantage that the Jenkins config is now part of the code itself and it allows for a compact representation of the Jenkins logic.
The script compiles the cli and gui config with gcc (via a Docker-environment, configuration can be found here) and runs the testrunner.
See the Jenkins job and also how the output of every step can be examined (click on the console icons).
Already includes (commented out) instructions for cross-compiling for Windows (see also #767).
Note: This will not replace the current Jenkins jobs in the near future because at the moment not the full Jenkins functionality can be used in a Workflow script.