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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21785: --------------------------------------------- also, PR builds probably can benefit from skipping some build steps for some jobs and might even want to happen at a finer granularity that the full component build. Thus I think there are a lot of reasons to have separate jobs for it. Is there a reason to why not having different jobs but with same configs ? (Besides we don't have templatized of jobs to easily manage this?) > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21657: --------------------------------------------- btw. suggestion of letting jenkins job just have the generated repository is a nice plan - except they are not accessible outside vpn. > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22260) Change 'Manage projects...' links to "New..." buttons

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22260?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22260: ---------------------------------- Assignee: Jeff MAURY > Change 'Manage projects...' links to "New..." buttons > ----------------------------------------------------- > > Key: JBIDE-22260 > URL: https://issues.jboss.org/browse/JBIDE-22260 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Jeff MAURY > Priority: Minor > Labels: application_wizard, docker, openshift_v3, ux > Fix For: 4.4.x > > > When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: > 1- click the manage project link > 2- click the New button in the manage projects wizards to open the New project wizard > 3- fill in the project name > 4- click ok to close the new project wizard > 5- click ok to close the manage projects wizards > => project list is reloaded > This could really be more streamlined to > 1- click the New button in the root wizard to open the New project wizard > 2- fill in the project name > 3- click ok to close the new project wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22260) Change 'Manage projects...' links to "New..." buttons

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22260?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22260: ------------------------------- Sprint: devex #115 May 2016 > Change 'Manage projects...' links to "New..." buttons > ----------------------------------------------------- > > Key: JBIDE-22260 > URL: https://issues.jboss.org/browse/JBIDE-22260 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Jeff MAURY > Priority: Minor > Labels: application_wizard, docker, openshift_v3, ux > Fix For: 4.4.x > > > When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: > 1- click the manage project link > 2- click the New button in the manage projects wizards to open the New project wizard > 3- fill in the project name > 4- click ok to close the new project wizard > 5- click ok to close the manage projects wizards > => project list is reloaded > This could really be more streamlined to > 1- click the New button in the root wizard to open the New project wizard > 2- fill in the project name > 3- click ok to close the new project wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21657: --------------------------------------------- "Ultimately my goal is to have jobs with just _master or _4.4.neon which will handle BOTH PRs and regular commits. See JBIDE-21785 for that work in progress" - I do not think this will work well, but I'll use JBIDE-21785 for commenting on it. > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22260) Change 'Manage projects...' links to "New..." buttons

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22260?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22260: ------------------------------- Sprint: devex #114 May 2016 (was: devex #115 May 2016) > Change 'Manage projects...' links to "New..." buttons > ----------------------------------------------------- > > Key: JBIDE-22260 > URL: https://issues.jboss.org/browse/JBIDE-22260 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Jeff MAURY > Priority: Minor > Labels: application_wizard, docker, openshift_v3, ux > Fix For: 4.4.x > > > When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: > 1- click the manage project link > 2- click the New button in the manage projects wizards to open the New project wizard > 3- fill in the project name > 4- click ok to close the new project wizard > 5- click ok to close the manage projects wizards > => project list is reloaded > This could really be more streamlined to > 1- click the New button in the root wizard to open the New project wizard > 2- fill in the project name > 3- click ok to close the new project wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21785: --------------------------------------------- isn't this going to create a bottleneck where PR trigger builds prevents actually running the main builds ? I would assume having the main builds separate from PR builds (even if they have same exact) configuration would be simpler/better. (reason why I wanted templatized jobs so it was easy to create copies with same config but slightly different behaviorf for where dependencies and deploys are from). > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-187) Add context menu to remove a connection [EBZ#493443]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-187?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-187. ------------------------------- Resolution: Done Patch merged upstream > Add context menu to remove a connection [EBZ#493443] > ---------------------------------------------------- > > Key: ERT-187 > URL: https://issues.jboss.org/browse/ERT-187 > Project: Eclipse Release Train > Issue Type: Enhancement > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Priority: Minor > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > There's already a toolbar action but adding the same command in the context menu when selecting a connection would would fill user's expectation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-186) Add "Execute shell" command in Docker Explorer view [EBZ#493422]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-186?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-186. ------------------------------- Resolution: Done Patch merged upstream > Add "Execute shell" command in Docker Explorer view [EBZ#493422] > ---------------------------------------------------------------- > > Key: ERT-186 > URL: https://issues.jboss.org/browse/ERT-186 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > The command is available in the Docker Containers view, but not in the Docker Explorer view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-185) NullPointerException when image has no tags [EBZ#493347]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-185?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-185. ------------------------------- Resolution: Done Fixed upstream > NullPointerException when image has no tags [EBZ#493347] > -------------------------------------------------------- > > Key: ERT-185 > URL: https://issues.jboss.org/browse/ERT-185 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > The following error occurred: > !ENTRY org.eclipse.core.jobs 4 2 2016-05-10 14:54:14.321 > !MESSAGE An internal error occurred during: "Refreshing Images...". > !STACK 0 > java.lang.NullPointerException > at java.util.ArrayList.<init>(ArrayList.java:177) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:847) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:785) > at org.eclipse.linuxtools.internal.docker.ui.commands.RefreshCommandHandler$2.run(RefreshCommandHandler.java:102) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > This happens on the "busybox' image that has no tags, as shown here: > $> docker inspect d167449 > [ > { > "Id": "sha256:d1674496321777c667b6a13597bf89752116f95ca248bd07a146948c2f119e4c", > "RepoTags": [], > "RepoDigests": [ > "busybox@sha256:7d3ce4e482101f0c484602dd6687c826bb8bef6295739088c58e84245845912e" > ], > ... > ] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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