September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24882) Can't rebuild releng image

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24882?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-24882: -------------------------------------- Resolved, releng server has been rebuilded [1]. The only change that I originally intended was to install rh-eclipse47.repo and rh-eclipse47-devstudio-snapshot-11.repo on all rhel7 slaves. So it shouldn't have any harmful aftermath. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/update-s... CC: [~nickboldt] > Can't rebuild releng image > -------------------------- > > Key: JBIDE-24882 > URL: https://issues.jboss.org/browse/JBIDE-24882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > It is not possible to rebuild "rhel7-x64-jbds-releng" image because update image pipeline \[1\] fails during cloning of mwqa-env-suite repository \[2\] > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Central... > \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite > {code} > MW QA environment configured > + echo 'MW QA environment configured' > + test_repo=git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git > + test='git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > + ssh -o PasswordAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o Loglevel=error -i /tmp/os.key.QYcvv9Sg hudson(a)10.8.242.82 'git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > Cloning into 'mwqa-env-suite'... > Bad owner or permissions on /home/hudson/.ssh/config > fatal: Could not read from remote repository. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24793) Add OpenShift.io login

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24793?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24793: ------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.x) > Add OpenShift.io login > ---------------------- > > Key: JBIDE-24793 > URL: https://issues.jboss.org/browse/JBIDE-24793 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Jeff MAURY > Fix For: 4.5.1.AM3 > > > Add an action to login to OpenShift.io based on stored credentials in the first class credential domain -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24985) Test test_pull_from_insecure_repository is failing

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24985?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24985. -------------------------------- Verified \[1\], closing. \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/update-s... > Test test_pull_from_insecure_repository is failing > -------------------------------------------------- > > Key: JBIDE-24985 > URL: https://issues.jboss.org/browse/JBIDE-24985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > The test test_pull_from_insecure_repository is failing with this output: > {console} > [branch_rhel7-x64-jbds-releng-lvalach] docker: > [branch_rhel7-x64-jbds-releng-lvalach] test_docker_installed_and_running > [branch_rhel7-x64-jbds-releng-lvalach] test_fetch_and_run_remote_image > [branch_rhel7-x64-jbds-releng-lvalach] Unable to find image 'debian:latest' locally > [branch_rhel7-x64-jbds-releng-lvalach] Trying to pull repository registry.access.redhat.com/debian ... > [branch_rhel7-x64-jbds-releng-lvalach] Trying to pull repository docker.io/library/debian ... > [branch_rhel7-x64-jbds-releng-lvalach] sha256:6ccbcbf362dbc4add74711cb774751b59cdfd7aed16c3c29aaecbea871952fe0: Pulling from docker.io/library/debian > [branch_rhel7-x64-jbds-releng-lvalach] 06b22ddb1913: Pulling fs layer > [branch_rhel7-x64-jbds-releng-lvalach] 06b22ddb1913: Verifying Checksum > [branch_rhel7-x64-jbds-releng-lvalach] 06b22ddb1913: Download complete > [branch_rhel7-x64-jbds-releng-lvalach] 06b22ddb1913: Pull complete > [branch_rhel7-x64-jbds-releng-lvalach] Digest: sha256:6ccbcbf362dbc4add74711cb774751b59cdfd7aed16c3c29aaecbea871952fe0 > [branch_rhel7-x64-jbds-releng-lvalach] Status: Downloaded newer image for docker.io/debian:latest > [branch_rhel7-x64-jbds-releng-lvalach] test_pull_from_insecure_repository > [branch_rhel7-x64-jbds-releng-lvalach] Trying to pull repository ce-registry.usersys.redhat.com/jboss-eap-6/eap64 ... > [branch_rhel7-x64-jbds-releng-lvalach] Pulling repository ce-registry.usersys.redhat.com/jboss-eap-6/eap64 > [branch_rhel7-x64-jbds-releng-lvalach] invalid character '<' looking for beginning of value > [branch_rhel7-x64-jbds-releng-lvalach] ASSERT:docker should be able to pull from insecure repositories > [branch_rhel7-x64-jbds-releng-lvalach] test_daemon_uses_default_tcp_port > [branch_rhel7-x64-jbds-releng-lvalach] test_talk_to_the_outer_world > [branch_rhel7-x64-jbds-releng-lvalach] > [branch_rhel7-x64-jbds-releng-lvalach] Ran 5 tests. > [branch_rhel7-x64-jbds-releng-lvalach] > [branch_rhel7-x64-jbds-releng-lvalach] FAILED (failures=1) > {console} > Whole log: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/update-s... > We probably need to update a repository URL. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24882) Can't rebuild releng image

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24882?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-24882: -------------------------------------- PR \[1\] has been replaced by \[2\]. \[1\] https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m... \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/c... > Can't rebuild releng image > -------------------------- > > Key: JBIDE-24882 > URL: https://issues.jboss.org/browse/JBIDE-24882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > It is not possible to rebuild "rhel7-x64-jbds-releng" image because update image pipeline \[1\] fails during cloning of mwqa-env-suite repository \[2\] > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Central... > \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite > {code} > MW QA environment configured > + echo 'MW QA environment configured' > + test_repo=git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git > + test='git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > + ssh -o PasswordAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o Loglevel=error -i /tmp/os.key.QYcvv9Sg hudson(a)10.8.242.82 'git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > Cloning into 'mwqa-env-suite'... > Bad owner or permissions on /home/hudson/.ssh/config > fatal: Could not read from remote repository. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24772) Refactoring: eliminate devstudio target platform; reuse jbosstools target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24772: ------------------------------- Description: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * *PR PENDING* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... * refactoring as per JBDS-3894 * documentation as per JBIDE-23510 was: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that: DONE ** update releng/publish scripts to look for https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.71.0.AM2... instead of jbdevstudiotarget-\*.zip: DONE in https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts: DONE in https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: DONE in JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... * refactoring as per JBDS-3894 * documentation as per JBIDE-23510 > Refactoring: eliminate devstudio target platform; reuse jbosstools target platform > ---------------------------------------------------------------------------------- > > Key: JBIDE-24772 > URL: https://issues.jboss.org/browse/JBIDE-24772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. > Changes: > * *PR PENDING* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 > * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that > * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... > * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... > * refactoring as per JBDS-3894 > * documentation as per JBIDE-23510 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24772) Refactoring: eliminate devstudio target platform; reuse jbosstools target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24772: ------------------------------- Description: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * *PR PENDING* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... * refactoring as per JBDS-3894 * documentation as per JBIDE-23510 was: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * *PR PENDING* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... * refactoring as per JBDS-3894 * documentation as per JBIDE-23510 > Refactoring: eliminate devstudio target platform; reuse jbosstools target platform > ---------------------------------------------------------------------------------- > > Key: JBIDE-24772 > URL: https://issues.jboss.org/browse/JBIDE-24772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places. > Changes: > * *PR PENDING* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 > * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that > * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... > * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... > * refactoring as per JBDS-3894 > * documentation as per JBIDE-23510 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24772) Refactoring: eliminate devstudio target platform; reuse jbosstools target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24772: ------------------------------- Description: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that: DONE ** update releng/publish scripts to look for https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.71.0.AM2... instead of jbdevstudiotarget-\*.zip: DONE in https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts: DONE in https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: DONE in JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... * refactoring as per JBDS-3894 * documentation as per JBIDE-23510 was: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that: DONE ** update releng/publish scripts to look for https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.71.0.AM2... instead of jbdevstudiotarget-\*.zip * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one * refactoring as per JBDS-3894 * documentation as per JBIDE-23510 > Refactoring: eliminate devstudio target platform; reuse jbosstools target platform > ---------------------------------------------------------------------------------- > > Key: JBIDE-24772 > URL: https://issues.jboss.org/browse/JBIDE-24772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. > Changes: > * jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 > * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that: DONE > ** update releng/publish scripts to look for https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.71.0.AM2... instead of jbdevstudiotarget-\*.zip: DONE in https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... > * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts: DONE in https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... > * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: DONE in JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... > * refactoring as per JBDS-3894 > * documentation as per JBIDE-23510 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24882) Can't rebuild releng image

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24882?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24882: --------------------------------- Git Pull Request: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/c... (was: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/c..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m...) > Can't rebuild releng image > -------------------------- > > Key: JBIDE-24882 > URL: https://issues.jboss.org/browse/JBIDE-24882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > It is not possible to rebuild "rhel7-x64-jbds-releng" image because update image pipeline \[1\] fails during cloning of mwqa-env-suite repository \[2\] > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Central... > \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite > {code} > MW QA environment configured > + echo 'MW QA environment configured' > + test_repo=git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git > + test='git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > + ssh -o PasswordAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o Loglevel=error -i /tmp/os.key.QYcvv9Sg hudson(a)10.8.242.82 'git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > Cloning into 'mwqa-env-suite'... > Bad owner or permissions on /home/hudson/.ssh/config > fatal: Could not read from remote repository. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24882) Can't rebuild releng image

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24882?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24882: --------------------------------- Git Pull Request: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/c..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m... (was: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/m..., https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-env-suite/c...) > Can't rebuild releng image > -------------------------- > > Key: JBIDE-24882 > URL: https://issues.jboss.org/browse/JBIDE-24882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > It is not possible to rebuild "rhel7-x64-jbds-releng" image because update image pipeline \[1\] fails during cloning of mwqa-env-suite repository \[2\] > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Central... > \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite > {code} > MW QA environment configured > + echo 'MW QA environment configured' > + test_repo=git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git > + test='git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > + ssh -o PasswordAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o Loglevel=error -i /tmp/os.key.QYcvv9Sg hudson(a)10.8.242.82 'git clone git@gitlab.mw.lab.eng.bos.redhat.com:dev-platform/mwqa-env-suite.git && ./mwqa-env-suite/run.sh jbds docker releng' > Cloning into 'mwqa-env-suite'... > Bad owner or permissions on /home/hudson/.ssh/config > fatal: Could not read from remote repository. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24934) Update org.eclipse.launchbar on Target Platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24934?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24934: ------------------------------------ org.eclipse.launchbar.* 2.1.1.201708231630 is now available from: * https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.71.0.AM2... and * https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.71.0.AM2... > Update org.eclipse.launchbar on Target Platform > ----------------------------------------------- > > Key: JBIDE-24934 > URL: https://issues.jboss.org/browse/JBIDE-24934 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.1.AM2 > > > Please update org.eclipse.launchbar on target platform, current version (2.1.1.201706131403) on target platform has a deadlock, which is fixed http://git.eclipse.org/c/cdt/org.eclipse.launchbar.git/commit/?id=64f1d0b... and http://git.eclipse.org/c/cdt/org.eclipse.launchbar.git/commit/?id=ff9289d... > I have tried version 2.1.1.201706151520, which looks good, but you can use newer version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 September 2017