[JBoss JIRA] (JBIDE-25006) ITests profile is active by default
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25006?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-25006:
---------------------------------------
[~nickboldt], you were right it was a good idea to check the jobs ;) It turned out that the green balls in the server.it.weekly job [1] were too good to be true - no tests were run.
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
> ITests profile is active by default
> -----------------------------------
>
> Key: JBIDE-25006
> URL: https://issues.jboss.org/browse/JBIDE-25006
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.1.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.5.1.AM2
>
>
> The intention is that if you run a build of anything depending on the parent pom, by default ITests profile is not active. But this doesn't work and it's always active unless you set -DskipITests=true from command line.
> The parent pom sets <skipITests>true</skipITests> here:
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
> And the ITests profile is activated if the skipITests property is not set at all:
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
> {code}
> <activation>
> <property>
> <name>!skipITests</name>
> </property>
> </activation>
> {code}
> We assumed that this would work but it turns out it does not work because profile activation only works with system properties and not properties in a pom.
> Pavol suggests simply removing the activation clause for that profile.
> [~nickboldt], what do you think of that? It seems simple enough. But who knows if there's hidden consequences to jobs that are used to the current behavior.
> Context: Builds of different repos started failing for us. Target platform max contains new RedDeer 2.0 and plugins in master still require RedDeer 1.x which is in target platform min. But it turned out that tpc.version is always set to target platform max which is not expected. So when investigating, we found that once the ITests profile is activated, it will set the tpc.version to max.
> This build breakage will disappear once TARGET_PLATFORM_VERSION_MIN is updated to the same version as TARGET_PLATFORM_VERSION_MAX - which is needed after the reddeer upgrade to 2.0. This is discussed in [1]. But we should still fix this.
> [1] https://issues.jboss.org/browse/JBIDE-25003?focusedCommentId=13461627&pag...
> Cc: [~psrna]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24964) HUDSON_STATIC_ENV not defined for windows and osx slaves
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24964?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-24964:
-------------------------------------
Assignee: Martin Malina (was: Pavol Srna)
> HUDSON_STATIC_ENV not defined for windows and osx slaves
> --------------------------------------------------------
>
> Key: JBIDE-24964
> URL: https://issues.jboss.org/browse/JBIDE-24964
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.5.x
>
>
> On windows and osx slaves, HUDSON_STATIC_ENV is not defined. On rhel7 slaves, it's defined as /home/hudson/static_build_env
> Could an equivalent path be set for other OSes, so we can benefit from this NFS-mounted shared space?
> Currently when we run itests on multiple OSes, we see stuff like this, when passing the path to -Ddownload.cache.directory=:
> {code:title=rhel7 - HUDSON_STATIC_ENV = /home/hudson/static_build_env}
> 16:05:48 [rhel7] $ /mnt/hudson_workspace/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn -s /tmp/settings2086504014812240990.xml -Djdk=openjdk-1.8 -Dlabel_exp=rhel7
> -Ddownload.cache.directory=/home/hudson/static_build_env/devstudio/download-cache
> -Dsurefire.timeout=10000 -DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=rhel7 -DBUILD_NUMBER=24 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last -Dsurefire.itests.timeout=10000 -Djbosstools.test.jre.7=/qa/tools/opt/x86_64/jdk1.7.0_last -Djbosstools.test.jre.6=/qa/tools/opt/x86_64/jdk1.6.0_last -Djbosstools.test.jre.5=/qa/tools/opt/x86_64/jdk1.5.0_last -DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum -DjgitDirtyWorkingTree=warning
> {code}
> {code:title=win81 - HUDSON_STATIC_ENV not defined}
> 16:05:51 [win81] $ cmd.exe /C "\mnt\hudson_workspace\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.9\bin\mvn.cmd -s C:\Users\jbossqa\AppData\Local\Temp\settings7229513778735293013.xml -Djdk=openjdk-1.8 -Dlabel_exp=win81
> -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache
> -Dsurefire.timeout=10000 "-DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=win81" -DBUILD_NUMBER=24 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=T:\opt\windows\amd64\jdk1.8.0_last -Dsurefire.itests.timeout=10000 -Djbosstools.test.jre.7=T:\opt\windows\amd64\jdk1.7.0_last -Djbosstools.test.jre.6=T:\opt\windows\amd64\jdk1.7.0_last -Djbosstools.test.jre.5=T:\opt\windows\amd64\jdk1.7.0_last -DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P "hudson,pack200,unified.target,maximum" -DjgitDirtyWorkingTree=warning && exit %%ERRORLEVEL%%"
> {code}
> {code:title=win10 - HUDSON_STATIC_ENV not defined}
> 16:05:48 [win10] $ cmd.exe /C "\mnt\hudson_workspace\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.9\bin\mvn.cmd -s C:\Users\jbossqa\AppData\Local\Temp\settings8339429706904285132.xml -Djdk=openjdk-1.8 -Dlabel_exp=win10
> -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache
> -Dsurefire.timeout=10000 "-DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=win10" -DBUILD_NUMBER=24 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=T:\opt\windows\amd64\jdk1.8.0_last -Dsurefire.itests.timeout=10000 -Djbosstools.test.jre.7=T:\opt\windows\amd64\jdk1.7.0_last -Djbosstools.test.jre.6=T:\opt\windows\amd64\jdk1.7.0_last -Djbosstools.test.jre.5=T:\opt\windows\amd64\jdk1.7.0_last -DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P "hudson,pack200,unified.target,maximum" -DjgitDirtyWorkingTree=warning && exit %%ERRORLEVEL%%"
> {code}
> {code:title=macosx - HUDSON_STATIC_ENV not defined}
> 16:05:46 [macosx] $ /jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn -s /var/folders/tp/hcfshtz152n2t8y4jfl08w140000gp/T/settings6780477723089804684.xml -Djdk=jdk1.8 -Dlabel_exp=macosx
> -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache
> -Dsurefire.timeout=10000 -DJOB_NAME=server.it.weekly/jdk=jdk1.8,label_exp=macosx -DBUILD_NUMBER=24 -DskipPrivateRequirements=false -Djbosstools.test.jre.8=/qa/tools/opt/osx/jdk1.8.0_last -Dsurefire.itests.timeout=10000 -Djbosstools.test.jre.7=/qa/tools/opt/osx/jdk1.7.0_last -Djbosstools.test.jre.6=/qa/tools/opt/osx/jdk1.8.0_last -Djbosstools.test.jre.5=/qa/tools/opt/osx/jdk1.8.0_last -DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum -DjgitDirtyWorkingTree=warning
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months