Hi, I have the teamconcert-plugin build passing! I even successfully released. The current job that I have is just a simple shell script type build. I don't have any flexibility in the build steps I can perform, unlike what I'm used to in a typical Jenkins install. You can see the job config here, https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/configure, but the shell script is just,
cd com.ibm.team.build.hjplugin mvn -X clean install I would like to be able to add a post build step to archive com.ibm.team.build.hjplugin/target/teamconcert.hpi so it can be smoke tested before a release. 1. How do I publish a pre-release plugin for others to smoke test? 2. Is my shell script correct, given I have two "projects" in my github repo? Any help would be appreciated. Thanks, Scott -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
