[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21012 at 10/26/15 4:35 PM:
--------------------------------------------------------------
So to recap, these changes are needed to the site/pom.xml and job config:
{quote}
1. define BUILD_NUMBER and timestamp for when building locally
2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/$\{project.name}-$\{project.version}.zip into the Nexus deployment.
3. set <classifier>${BUILD_ALIAS}</classifier> if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54
{code}
- $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS}
+ $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER}
{code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156
One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :(
To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal.
was (Author: nickboldt):
So to recap, these changes are needed to the site/pom.xml and job config:
{quote}
1. define BUILD_NUMBER and timestamp for when building locally
2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/\${project.name}-\${project.version}.zip into the Nexus deployment.
3. set <classifier>${BUILD_ALIAS}</classifier> if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54
{code}
- $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS}
+ $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER}
{code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156
One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :(
To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal.
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21012 at 10/26/15 4:35 PM:
--------------------------------------------------------------
So to recap, these changes are needed to the site/pom.xml and job config:
{quote}
1. define BUILD_NUMBER and timestamp for when building locally
2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/$\{project.name}-$\{project.version}.zip into the Nexus deployment.
3. set <classifier>$\{BUILD_ALIAS}</classifier> if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54
{code}
- $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS}
+ $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER}
{code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156
One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :(
To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal.
was (Author: nickboldt):
So to recap, these changes are needed to the site/pom.xml and job config:
{quote}
1. define BUILD_NUMBER and timestamp for when building locally
2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/$\{project.name}-$\{project.version}.zip into the Nexus deployment.
3. set <classifier>${BUILD_ALIAS}</classifier> if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54
{code}
- $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS}
+ $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER}
{code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156
One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :(
To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal.
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21012:
------------------------------------
So to recap, these changes are needed to the site/pom.xml and job config:
{quote}
1. define BUILD_NUMBER and timestamp for when building locally
2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/${project.name}-${project.version}.zip into the Nexus deployment.
3. set <classifier>${BUILD_ALIAS}</classifier> if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54
{code}
- $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS}
+ $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER}
{code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156
One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :(
To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal.
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21012 at 10/26/15 4:34 PM:
--------------------------------------------------------------
So to recap, these changes are needed to the site/pom.xml and job config:
{quote}
1. define BUILD_NUMBER and timestamp for when building locally
2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/\${project.name}-\${project.version}.zip into the Nexus deployment.
3. set <classifier>${BUILD_ALIAS}</classifier> if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54
{code}
- $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS}
+ $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER}
{code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156
One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :(
To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal.
was (Author: nickboldt):
So to recap, these changes are needed to the site/pom.xml and job config:
{quote}
1. define BUILD_NUMBER and timestamp for when building locally
2. call build-helper-maven-plugin::attach-artifacts::attach-artifact to connect the ../site/target/${project.name}-${project.version}.zip into the Nexus deployment.
3. set <classifier>${BUILD_ALIAS}</classifier> if you want to ensure that there's no overlap of the Alpha2x (BUILD_ALIAS=Alpha2) and master (BUILD_ALIAS=Beta1) branches, so we don't accidentally get the wrong bits aggregated.{quote} -- https://github.com/jbosstools/jbosstools-freemarker/pull/54
{code}
- $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS}
+ $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository -Djbosstools_site_stream=${jbosstools_site_stream} ${MAVEN_FLAGS} -Dtimestamp=${timestamp} -DBUILD_NUMBER=${BUILD_NUMBER}
{code} -- https://github.com/jbdevstudio/jbdevstudio-ci/pull/156
One thing to confirm here is that we can have more than one zip artifact in https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
I'm not 100% sure this is possible; thus instead of having a collision between two different 1.5.100-SNAPSHOT update sites (one from Alpha2x branch with BUILD_ALIAS=Alpha2; one from master branch with BUILD_ALIAS=Beta1), we will instead get alternating 404s as one or the other zip vanishes. :(
To make this work, we might have to DISABLE master branch deployment to nexus while code frozen for the Alpha2x branch. This is of course non-ideal.
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21012:
------------------------------------
I was halfway through sending an email to ci-issues@ to report that the unzip process wasn't working, when suddenly this appeared:
https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
But when I look elsewhere (in another browser) this is still empty:
https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
So... if I just use the BUILD_ALIAS we can have reusable URLs for all of a given branch (for any given BUILD_ALIAS & project.version combination).
So, I did that... updated the PR, and kicked a fresh build B311.
Results:
* *{color:green}This now exists:{color}* https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
* *{color:red}This has vanished / is 404'd:{color}* https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
HOWEVER... seems there's about a 20 min lag between the Jenkins job and the unzip URL appearing.
So... we can use this approach, but it's a bit slower than the lag on download.jboss.org.
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months