May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-21785. ------------------------------ Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha3) Resolution: Rejected Closing - rejected. > enable hybrid jobs which can handle both commits and PRs with different publishing patterns > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21785 > URL: https://issues.jboss.org/browse/JBIDE-21785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Currently we have jobs which handle building from commits, then publishing to a builds/ folder. > And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then publishing to a pulls/ folder. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > Now we need to combine the jobs so that we can do both deployments from the same job, eg., > {code} > if [[ ! ${ghprbPullId} ]]; then > mvnStep1="clean install -DskipTests" # build without tests > mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder > mvnStep3="verify" # run tests & fail job if problems found > else > mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail > mvnStep2="NONE" > mvnStep3="NONE" > fi > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21785: ------------------------------------ Since it's problematic to make PR jobs ALSO build regular commits, I have to agree with you both -- we need separate jobs for building PRs and for building commits. :( So much for more build-related artifacts and yet another reason I need to get templatized jobs working ASAP. :D > enable hybrid jobs which can handle both commits and PRs with different publishing patterns > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21785 > URL: https://issues.jboss.org/browse/JBIDE-21785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > > Currently we have jobs which handle building from commits, then publishing to a builds/ folder. > And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then publishing to a pulls/ folder. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > Now we need to combine the jobs so that we can do both deployments from the same job, eg., > {code} > if [[ ! ${ghprbPullId} ]]; then > mvnStep1="clean install -DskipTests" # build without tests > mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder > mvnStep3="verify" # run tests & fail job if problems found > else > mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail > mvnStep2="NONE" > mvnStep3="NONE" > fi > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22297) Update failing test to be in synch with fix to - JBIDE-21632

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22297?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-22297. -------------------------------- Resolution: Done > Update failing test to be in synch with fix to - JBIDE-21632 > ------------------------------------------------------------ > > Key: JBIDE-22297 > URL: https://issues.jboss.org/browse/JBIDE-22297 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.1.1.Alpha1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.1.1.Alpha1 > > > See: JBIDE-21632 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13671: ------------------------------------ We could start comparing with latest /development/ instead of /stable/ if we wanted. But that would require a parent pom bump to ensure that the BUILD_ALIAS increments for each major milestone? > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.x > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13671: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha2) > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.x > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21785: ------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > enable hybrid jobs which can handle both commits and PRs with different publishing patterns > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21785 > URL: https://issues.jboss.org/browse/JBIDE-21785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > > Currently we have jobs which handle building from commits, then publishing to a builds/ folder. > And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then publishing to a pulls/ folder. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > Now we need to combine the jobs so that we can do both deployments from the same job, eg., > {code} > if [[ ! ${ghprbPullId} ]]; then > mvnStep1="clean install -DskipTests" # build without tests > mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder > mvnStep3="verify" # run tests & fail job if problems found > else > mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail > mvnStep2="NONE" > mvnStep3="NONE" > fi > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22297) Update failing test to be in synch with fix to - JBIDE-21632

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22297?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-22297: --------------------------------- Fix Version/s: 4.1.1.Alpha1 > Update failing test to be in synch with fix to - JBIDE-21632 > ------------------------------------------------------------ > > Key: JBIDE-22297 > URL: https://issues.jboss.org/browse/JBIDE-22297 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.1.1.Alpha1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.1.1.Alpha1 > > > See: JBIDE-21632 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20996: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha2) > DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20996 > URL: https://issues.jboss.org/browse/JBIDE-20996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, upstream > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.x > > > It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. > Is there anything we could do to make this workflow easier. > Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22280) Investigate why wrong JBT IS site is used in JBT 4.4.0.Alpha1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22280?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22280. ------------------------------ Resolution: Done Fixed by Paul (?) downstream in JBTIS. > Investigate why wrong JBT IS site is used in JBT 4.4.0.Alpha1 > ------------------------------------------------------------- > > Key: JBIDE-22280 > URL: https://issues.jboss.org/browse/JBIDE-22280 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > After staging 4.4.0.Alpha1: > * JBT IS stuff is using the wrong URL - > !MESSAGE Problems occurred while performing installation: No repository found at http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta.... > * JBT IS cannot install -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22281) Investigate why JBT 4.4.0.Alpha1 loads too many update sites (for EA and IS)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22281?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22281: ------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Investigate why JBT 4.4.0.Alpha1 loads too many update sites (for EA and IS) > ---------------------------------------------------------------------------- > > Key: JBIDE-22281 > URL: https://issues.jboss.org/browse/JBIDE-22281 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > * JBT 4.4.0.Alpha1 loads too many update sites: > 1. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/ > 2. JBoss Tools - Core + Central Update Site http://download.jboss.org/jbosstools/neon/staging/updates/discovery.early... > 3. http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > 4. http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016