April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20901) JBDS update site builds produces update site zip TWICE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20901?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20901: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > JBDS update site builds produces update site zip TWICE > ------------------------------------------------------ > > Key: JBIDE-20901 > URL: https://issues.jboss.org/browse/JBIDE-20901 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > JBDS build creates the update site zip TWICE: > {code} > [INFO] --- tycho-p2-repository-plugin:0.23.1:archive-repository (default-archive-repository) @ com.jboss.devstudio.core.site --- > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.23.1:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/repository/web/site.css found; using default. > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21657: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21066) update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21066: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > Attachments: terminal.png, Terminal.webm, tm.term.view.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21834) remove "component-site" builder in jbosstools-build-sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21834?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21834: ------------------------------- Story Points: 1 Sprint: devex #114 May 2017 > remove "component-site" builder in jbosstools-build-sites > --------------------------------------------------------- > > Key: JBIDE-21834 > URL: https://issues.jboss.org/browse/JBIDE-21834 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.0.Alpha2 > > > Seems that the "component-site/pom.xml no longer works -- based on the README, it was last used for Kepler or Luna. > https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... > So either we make this work or we remove it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21796) [bzira] [jiralint] HTTP 400 errors creating ERT JIRAs from Eclipse BZ when BZ is in ASSIGNED state

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21796?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21796: ------------------------------- Fix Version/s: 4.4.0.Alpha3 > [bzira] [jiralint] HTTP 400 errors creating ERT JIRAs from Eclipse BZ when BZ is in ASSIGNED state > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21796 > URL: https://issues.jboss.org/browse/JBIDE-21796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > Attachments: bzira.log.txt > > > Was reported today that Eclipse bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=488373 was not created as an ERT issue. > So I re-ran bzira like this: > {code} > python -W ignore bzira.py -u JIRA_USER -p JIRA_PWD -s https://issues.jboss.org -S 2016-02-24 -v > {code} > And got this when creating ERT-82: > {code} > [INFO] Created https://issues.jboss.org/browse/ERT-82 > JiraError HTTP 400 > text: It seems that you have tried to perform a workflow operation (Start Progress) that is not valid for the current state of this issue (ERT-82). The likely cause is that somebody has changed the issue recently, please look at the issue history for details. > url: https://issues.jboss.org/rest/api/2/issue/ERT-82/transitions > {code} > Curiously, the same error was thrown when creating ERT-88: > {code} > [INFO] Created https://issues.jboss.org/browse/ERT-88 > > Jira ERT-82 gave following errors: > Could not perform transition{'id': '4'} error: JiraError HTTP 400 > text: It seems that you have tried to perform a workflow operation (Start Progress) that is not valid for the current state of this issue (ERT-82). The likely cause is that somebody has changed the issue recently, please look at the issue history for details. > url: https://issues.jboss.org/rest/api/2/issue/ERT-82/transitions > {code} > full log: [^bzira.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21796) [bzira] [jiralint] HTTP 400 errors creating ERT JIRAs from Eclipse BZ when BZ is in ASSIGNED state

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21796?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21796: ------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > [bzira] [jiralint] HTTP 400 errors creating ERT JIRAs from Eclipse BZ when BZ is in ASSIGNED state > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21796 > URL: https://issues.jboss.org/browse/JBIDE-21796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > Attachments: bzira.log.txt > > > Was reported today that Eclipse bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=488373 was not created as an ERT issue. > So I re-ran bzira like this: > {code} > python -W ignore bzira.py -u JIRA_USER -p JIRA_PWD -s https://issues.jboss.org -S 2016-02-24 -v > {code} > And got this when creating ERT-82: > {code} > [INFO] Created https://issues.jboss.org/browse/ERT-82 > JiraError HTTP 400 > text: It seems that you have tried to perform a workflow operation (Start Progress) that is not valid for the current state of this issue (ERT-82). The likely cause is that somebody has changed the issue recently, please look at the issue history for details. > url: https://issues.jboss.org/rest/api/2/issue/ERT-82/transitions > {code} > Curiously, the same error was thrown when creating ERT-88: > {code} > [INFO] Created https://issues.jboss.org/browse/ERT-88 > > Jira ERT-82 gave following errors: > Could not perform transition{'id': '4'} error: JiraError HTTP 400 > text: It seems that you have tried to perform a workflow operation (Start Progress) that is not valid for the current state of this issue (ERT-82). The likely cause is that somebody has changed the issue recently, please look at the issue history for details. > url: https://issues.jboss.org/rest/api/2/issue/ERT-82/transitions > {code} > full log: [^bzira.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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.Alpha2 (was: 4.4.0.Alpha1) > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21834) remove "component-site" builder in jbosstools-build-sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21834?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21834: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > remove "component-site" builder in jbosstools-build-sites > --------------------------------------------------------- > > Key: JBIDE-21834 > URL: https://issues.jboss.org/browse/JBIDE-21834 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.0.Alpha2 > > > Seems that the "component-site/pom.xml no longer works -- based on the README, it was last used for Kepler or Luna. > https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... > So either we make this work or we remove it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22205) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Discovery]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22205?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22205. ------------------------------ Resolution: Rejected Nothing on this list should have been pushed to master. Except for 2 items, these are all "bump version" commits. Can we exclude those, [~rob.stryker] ? > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Discovery] > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22205 > URL: https://issues.jboss.org/browse/JBIDE-22205 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central-update > Reporter: Rob Stryker > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Discovery]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-discovery at https://github.com/jbosstools/jbosstools-discovery/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "9ad468" is the last common ancestor of jbosstools-4.3.x and master > 9ad468 is 22 commits ago in branch master > 9ad468 is 26 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-discovery//commit/0287cfbb7ba3bd... > - https://github.com/jbosstools/jbosstools-discovery//commit/5e6fe574836e26... > - https://github.com/jbosstools/jbosstools-discovery//commit/54c7d078d4457d... > - https://github.com/jbosstools/jbosstools-discovery//commit/5583661a5d4324... > - https://github.com/jbosstools/jbosstools-discovery//commit/2465d0c3e5d411... > - https://github.com/jbosstools/jbosstools-discovery//commit/3b46e9d67efb62... > - https://github.com/jbosstools/jbosstools-discovery//commit/2f3afda514dcfb... > - https://github.com/jbosstools/jbosstools-discovery//commit/c5ee5345fc4583... > - https://github.com/jbosstools/jbosstools-discovery//commit/ad8de6ee6b9af8... > - https://github.com/jbosstools/jbosstools-discovery//commit/12568a875d10f0... > - https://github.com/jbosstools/jbosstools-discovery//commit/56751d5fcc1816... > - https://github.com/jbosstools/jbosstools-discovery//commit/5dd62f01020764... > - https://github.com/jbosstools/jbosstools-discovery//commit/5c72ceaf88efb8... > - https://github.com/jbosstools/jbosstools-discovery//commit/61f5c5a7bb1ec9... > - https://github.com/jbosstools/jbosstools-discovery//commit/39b63626333010... > - https://github.com/jbosstools/jbosstools-discovery//commit/90668d7f93d840... > - https://github.com/jbosstools/jbosstools-discovery//commit/df214c5bb0c9fa... > - https://github.com/jbosstools/jbosstools-discovery//commit/ed4031bed09e4e... > - https://github.com/jbosstools/jbosstools-discovery//commit/aa7a93a5b354bc... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Discovery task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22275) oc version is not recognized

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22275 at 4/29/16 10:38 AM: ------------------------------------------------------------------------- OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two hyphens, like in oc v1.2.0--rc2 It can be replaced with {code} "oc v([0-9\\.-\\.]*)(?:-(?:([0-9]+)-)?(.*))?" {code} was (Author: scabanovich): OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two hyphens, like in oc v1.2.0--rc2 It can be replaced with {code} "oc v([0-9\\.-\\.]*)(?:-([0-9]*)-(.*))?" {code} > oc version is not recognized > ---------------------------- > > Key: JBIDE-22275 > URL: https://issues.jboss.org/browse/JBIDE-22275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: oc_warning.png > > > Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0. > !oc_warning.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016