[jbosstools-issues] [JBoss JIRA] (JBIDE-22819) wrap staging build process with a jenkins job
Nick Boldt (JIRA)
issues at jboss.org
Fri Aug 12 17:23:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278497#comment-13278497 ]
Nick Boldt edited comment on JBIDE-22819 at 8/12/16 5:22 PM:
-------------------------------------------------------------
0. Overall buildflow job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow-push-to-staging_master/
1. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-01-check-versions-branches-root-poms_master/}
// Verify correct version set in org.jboss.tools.foundation.core and devstudio.core.central
// Verify all branches have been created & all root poms point to the correct parent pom version.
{code}
1a. By hand:
* Disable jobs [so far has to be done by hand because of permissions]
1b. Using the buildflow or by hand:
* Build Discovery Sites
2. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-02-copy-builds-and-update-sites_master/}
// Copy & rename builds & update sites from "snapshots" to "staging"
{code}
Still To do:
{code}
// 3. Verify sites are correctly populated using curl | grep to check for contents / 404s; fail if anything missing
// 4. TODO: generate PR for Update http://download.jboss.org/jbosstools/neon/staging/updates/
// 5. merge in IS content
// 6. TODO: generate PR for Release the latest staging site to ide-config.properties
// 7. generate notification emails
{code}
8. By hand:
* re-enable jobs [may have to be done by hand because of permissions]
* disable the buildflow and push-to-staging jobs [may have to be done by hand because of permissions]
was (Author: nickboldt):
0. Overall buildflow job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow-push-to-staging_master/
1. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-01-check-versions-branches-root-poms_master/}
// Verify correct version set in org.jboss.tools.foundation.core and devstudio.core.central
// Verify all branches have been created & all root poms point to the correct parent pom version.
{code}
1a. By hand:
* Disable jobs [so far has to be done by hand because of permissions]
1b. Using the buildflow or by hand:
* Build Discovery Sites
2. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-staging-02-copy-builds-and-update-sites_master/}
// Copy & rename builds & update sites from "snapshots" to "staging"
{code}
Still To do:
{code}
// 3. Verify sites are correctly populated using curl | grep to check for contents / 404s; fail if anything missing
// 4. TODO: generate PR for Update http://download.jboss.org/jbosstools/neon/staging/updates/
// 5. merge in IS content
// 6. TODO: generate PR for Release the latest staging site to ide-config.properties
// 7. generate notification emails
{code}
8. By hand:
* re-enable jobs [may have to be done by hand because of permissions]
* disable this job [may have to be done by hand because of permissions]
> wrap staging build process with a jenkins job
> ---------------------------------------------
>
> Key: JBIDE-22819
> URL: https://issues.jboss.org/browse/JBIDE-22819
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> Job requires about 13 params:
> {code}
> version (JBT and JBDS)
> versionWithRespin (JBT and JBDS)
> versionWithRespin_PREV (JBT and JBDS)
> target platforms (min, max, central)
> respin # (- or a, b, c)
> devsuite installerExe url
> stream_JBT=master # or 4.4.neon
> stream_DS=master # or 10.0.neon
> {code}
> See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_guide/10 for the steps to convert into a job
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list