-
Task
-
Resolution: Fixed
-
Minor
-
None
There is no official release flow for Jenkisnfile Runner, currently it's not uploaded to artifactory and jenkinsx is using a commit of the jenkinsfile runner. In some cases a build from tag is required (e.g. Custom WAR Packager) and right now only commits can be used.
This could be achieved by:
- mvn release flow - app assembler target directory needs to be zipped first to be used as the artifact.
- Example of ZIP packaging 1: https://github.com/kibana-community/kibana4-static/blob/master/pom.xml
Acceptance criteria
- Tags in github
- Demos use tags instead of commit for CWP and Jenkinsfile runner
- Changelog
- Standard releases to Jenkins artifactory
- The first BETA release is performed (1.0-beta-1)
- Get permissions to publish in artifactory
Missing test: ensure that class loading happens from the bundle of Jenkins core and not from the version that Jenkinsfile runner provides