[JBoss JIRA] (JBIDE-24010) org.jboss.tools.openshift.client: Version has moved backwards
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24010?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24010:
-------------------------------
Description:
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines
(default) on project org.jboss.tools.openshift.client: Version have moved backwards for
(org.jboss.tools.openshift.client/3.3.2.AM1-v20170224-1533-B1868).
Baseline has 3.3.2.Final-v20170217-1414-B33) with delta: 0.0.0
{code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
Solution: upversion your client plugin or make it not use the BUILD_ALIAS in its version (so it's only got a timestamp).
was:
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.openshift.client: Version have moved backwards for (org.jboss.tools.openshift.client/3.3.2.AM1-v20170224-1533-B1868). Baseline has 3.3.2.Final-v20170217-1414-B33) with delta: 0.0.0
{code}
Solution: upversion your client plugin or make it not use the BUILD_ALIAS in its version (so it's only got a timestamp).
> org.jboss.tools.openshift.client: Version has moved backwards
> -------------------------------------------------------------
>
> Key: JBIDE-24010
> URL: https://issues.jboss.org/browse/JBIDE-24010
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> {code}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines
> (default) on project org.jboss.tools.openshift.client: Version have moved backwards for
> (org.jboss.tools.openshift.client/3.3.2.AM1-v20170224-1533-B1868).
> Baseline has 3.3.2.Final-v20170217-1414-B33) with delta: 0.0.0
> {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
> Solution: upversion your client plugin or make it not use the BUILD_ALIAS in its version (so it's only got a timestamp).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-24010) org.jboss.tools.openshift.client: Version has moved backwards
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-24010:
----------------------------------
Summary: org.jboss.tools.openshift.client: Version has moved backwards
Key: JBIDE-24010
URL: https://issues.jboss.org/browse/JBIDE-24010
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.0.AM1
Reporter: Nick Boldt
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.openshift.client: Version have moved backwards for (org.jboss.tools.openshift.client/3.3.2.AM1-v20170224-1533-B1868). Baseline has 3.3.2.Final-v20170217-1414-B33) with delta: 0.0.0
{code}
Solution: upversion your client plugin or make it not use the BUILD_ALIAS in its version (so it's only got a timestamp).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23962) problem creating temp folder when publishing discovery site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23962?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23962:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.4.AM1)
> problem creating temp folder when publishing discovery site
> -----------------------------------------------------------
>
> Key: JBIDE-23962
> URL: https://issues.jboss.org/browse/JBIDE-23962
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central-update
> Affects Versions: 4.4.3.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> {code}
> Changing to: /www_htdocs/devstudio/
> sftp> mkdir 10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_14-24-05-B94/all/repo
> [INFO] rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-discovery_4.4.neon/sources/jbdevstudio/com.jboss.jbds.central.discovery/target/discovery-site/* devstudio@10.5.105.197:/www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_14-24-05-B94/all/repo//
> [DEBUG] Symlink[BT] devstudio@10.5.105.197:/www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/latest -> 2017-02-17_14-24-05-B94
> Logfile: /tmp/tmp.uWSYW30193/jbosstools-cleanup.sh.log.20170217-1428.txt
> Check for 10.0/snapshots/builds builds more than 2 days old; keep minimum 2 builds per branch (linked in composite: 2)
> Check /www_htdocs/devstudio/10.0/snapshots/builds/ for dirs matching /jbosstools-discovery.central_4.4.neon/ ...
> > Check /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon...
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_14-24-05-B94 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_06-34-11-B90 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_05-15-54-B89 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_03-30-59-B88 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_02-38-20-B87 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_00-49-19-B86 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_00-05-16-B85 (0d)
> > Check /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon...
> Generate metadata for first 2 of 7 subdir(s) in /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/ (siteName = 10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon
> mktemp: invalid option -- -
> Usage: mktemp [-V] | [-dqtu] [-p prefix] [template]
> real 0m48.690s
> user 0m0.259s
> sys 0m0.303s
> + /mnt/hudson_workspace/workspace/jbosstools-discovery_4.4.neon/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-discovery_4.4.neon/sources/jbdevstudio/com.jboss.jbds.central.discovery.earlyaccess/target/discovery-site -t 10.0/snapshots/builds/jbosstools-discovery.earlyaccess_4.4.neon/2017-02-17_14-24-05-B94/all/repo/ -DESTINATION devstudio@10.5.105.197:/www_htdocs/devstudio
> [DEBUG] BUILD_TIMESTAMP = 2017-02-17_14-24-05
> [DEBUG] RSYNCFLAGS =
> Connecting to 10.5.105.197...{code}
> -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23962) problem creating temp folder when publishing discovery site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23962?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-23962.
------------------------------
Resolution: Done
> problem creating temp folder when publishing discovery site
> -----------------------------------------------------------
>
> Key: JBIDE-23962
> URL: https://issues.jboss.org/browse/JBIDE-23962
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central-update
> Affects Versions: 4.4.3.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> {code}
> Changing to: /www_htdocs/devstudio/
> sftp> mkdir 10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_14-24-05-B94/all/repo
> [INFO] rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-discovery_4.4.neon/sources/jbdevstudio/com.jboss.jbds.central.discovery/target/discovery-site/* devstudio@10.5.105.197:/www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_14-24-05-B94/all/repo//
> [DEBUG] Symlink[BT] devstudio@10.5.105.197:/www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/latest -> 2017-02-17_14-24-05-B94
> Logfile: /tmp/tmp.uWSYW30193/jbosstools-cleanup.sh.log.20170217-1428.txt
> Check for 10.0/snapshots/builds builds more than 2 days old; keep minimum 2 builds per branch (linked in composite: 2)
> Check /www_htdocs/devstudio/10.0/snapshots/builds/ for dirs matching /jbosstools-discovery.central_4.4.neon/ ...
> > Check /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon...
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_14-24-05-B94 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_06-34-11-B90 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_05-15-54-B89 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_03-30-59-B88 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_02-38-20-B87 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_00-49-19-B86 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_00-05-16-B85 (0d)
> > Check /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon...
> Generate metadata for first 2 of 7 subdir(s) in /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/ (siteName = 10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon
> mktemp: invalid option -- -
> Usage: mktemp [-V] | [-dqtu] [-p prefix] [template]
> real 0m48.690s
> user 0m0.259s
> sys 0m0.303s
> + /mnt/hudson_workspace/workspace/jbosstools-discovery_4.4.neon/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-discovery_4.4.neon/sources/jbdevstudio/com.jboss.jbds.central.discovery.earlyaccess/target/discovery-site -t 10.0/snapshots/builds/jbosstools-discovery.earlyaccess_4.4.neon/2017-02-17_14-24-05-B94/all/repo/ -DESTINATION devstudio@10.5.105.197:/www_htdocs/devstudio
> [DEBUG] BUILD_TIMESTAMP = 2017-02-17_14-24-05
> [DEBUG] RSYNCFLAGS =
> Connecting to 10.5.105.197...{code}
> -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23768) Publish tagged version of jboss tools parent pom to public repository
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23768 at 2/24/17 4:48 PM:
-------------------------------------------------------------
So, because the workflow is different for snapshots and releases, I've done this in the parent pom jobs [1], [2]:
{code}
pom=${WORKSPACE}/sources/parent/pom.xml
pomVersion=$(grep "<version>" ${pom} | head -1 | sed -e "s#.*<version>\(.\+\)</version>.*#\1#")
echo "pomVersion=${pomVersion}" > ${WORKSPACE}/env.properties # eg., 4.4.4.Final
MVN="/qa/tools/opt/maven3-latest/bin/mvn -Dmaven.repo.local=${WORKSPACE}/.repository/"
pushd ${WORKSPACE}/sources/parent/
if [[ ${pomVersion} == *"-SNAPSHOT" ]]; then
${MVN} deploy
else
${MVN} clean deploy -DskipRemoteStaging=true -DstagingDescription="[${JOB_NAME} ${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: deploy to local"
${MVN} nexus-staging:deploy-staged -DstagingDescription="[${JOB_NAME} ${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: deploy to stage + close"
${MVN} nexus-staging:release -DstagingDescription="[${JOB_NAME} ${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: release"
fi{code}
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
[2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
was (Author: nickboldt):
So, because the workflow is different for snapshots and releases, I've done this in the parent pom jobs:
{code}
pom=${WORKSPACE}/sources/parent/pom.xml
pomVersion=$(grep "<version>" ${pom} | head -1 | sed -e "s#.*<version>\(.\+\)</version>.*#\1#")
echo "pomVersion=${pomVersion}" > ${WORKSPACE}/env.properties # eg., 4.4.4.Final
MVN="/qa/tools/opt/maven3-latest/bin/mvn -Dmaven.repo.local=${WORKSPACE}/.repository/"
pushd ${WORKSPACE}/sources/parent/
if [[ ${pomVersion} == *"-SNAPSHOT" ]]; then
${MVN} deploy
else
${MVN} clean deploy -DskipRemoteStaging=true -DstagingDescription="[${JOB_NAME} ${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: deploy to local"
${MVN} nexus-staging:deploy-staged -DstagingDescription="[${JOB_NAME} ${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: deploy to stage + close"
${MVN} nexus-staging:release -DstagingDescription="[${JOB_NAME} ${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: release"
fi{code}
> Publish tagged version of jboss tools parent pom to public repository
> ---------------------------------------------------------------------
>
> Key: JBIDE-23768
> URL: https://issues.jboss.org/browse/JBIDE-23768
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.4.2.Final, 4.4.3.AM1
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.4.3.Final
>
>
> it will allow Fuse Tooling (and other dependent projects) to have tagged version of their parent pom for tagged release.
> i'm talking about org.jboss.tools:parent
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23962) problem creating temp folder when publishing discovery site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23962?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23962:
------------------------------------
No longer seeing the above error; instead we have:
{code}
Generate metadata for first 2 of 2 subdir(s) in /www_htdocs/devstudio/11/snapshots/builds/jbosstools-discovery.central_master/ (siteName = 11/snapshots/builds/jbosstools-discovery.central_master
real 0m32.795s
user 0m0.222s
sys 0m0.225s
+ /mnt/hudson_workspace/workspace/jbosstools-discovery_master/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-discovery_master/sources/jbdevstudio/com.jboss.jbds.central.discovery.earlyaccess/target/discovery-site -t 11/snapshots/builds/jbosstools-discovery.earlyaccess_master/2017-02-24_21-29-49-B7494/all/repo/ -DESTINATION devstudio@10.5.105.197:/www_htdocs/devstudio
{code}
In these console logs:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
> problem creating temp folder when publishing discovery site
> -----------------------------------------------------------
>
> Key: JBIDE-23962
> URL: https://issues.jboss.org/browse/JBIDE-23962
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central-update
> Affects Versions: 4.4.3.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM1
>
>
> {code}
> Changing to: /www_htdocs/devstudio/
> sftp> mkdir 10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_14-24-05-B94/all/repo
> [INFO] rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-discovery_4.4.neon/sources/jbdevstudio/com.jboss.jbds.central.discovery/target/discovery-site/* devstudio@10.5.105.197:/www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_14-24-05-B94/all/repo//
> [DEBUG] Symlink[BT] devstudio@10.5.105.197:/www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/latest -> 2017-02-17_14-24-05-B94
> Logfile: /tmp/tmp.uWSYW30193/jbosstools-cleanup.sh.log.20170217-1428.txt
> Check for 10.0/snapshots/builds builds more than 2 days old; keep minimum 2 builds per branch (linked in composite: 2)
> Check /www_htdocs/devstudio/10.0/snapshots/builds/ for dirs matching /jbosstools-discovery.central_4.4.neon/ ...
> > Check /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon...
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_14-24-05-B94 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_06-34-11-B90 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_05-15-54-B89 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_03-30-59-B88 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_02-38-20-B87 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_00-49-19-B86 (0d)
> + /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/2017-02-17_00-05-16-B85 (0d)
> > Check /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon...
> Generate metadata for first 2 of 7 subdir(s) in /www_htdocs/devstudio/10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon/ (siteName = 10.0/snapshots/builds/jbosstools-discovery.central_4.4.neon
> mktemp: invalid option -- -
> Usage: mktemp [-V] | [-dqtu] [-p prefix] [template]
> real 0m48.690s
> user 0m0.259s
> sys 0m0.303s
> + /mnt/hudson_workspace/workspace/jbosstools-discovery_4.4.neon/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-discovery_4.4.neon/sources/jbdevstudio/com.jboss.jbds.central.discovery.earlyaccess/target/discovery-site -t 10.0/snapshots/builds/jbosstools-discovery.earlyaccess_4.4.neon/2017-02-17_14-24-05-B94/all/repo/ -DESTINATION devstudio@10.5.105.197:/www_htdocs/devstudio
> [DEBUG] BUILD_TIMESTAMP = 2017-02-17_14-24-05
> [DEBUG] RSYNCFLAGS =
> Connecting to 10.5.105.197...{code}
> -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month