January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25515) GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25515?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-25515: --------------------------------- Sprint: (was: devex #143 January 2018) > GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25515 > URL: https://issues.jboss.org/browse/JBIDE-25515 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.AM3 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.2.Final > > > A lot of installer tests are failing because after last update of Jenkins script \[1\] GetJBDSInstallerLink.groovy hasn't permission to use some features of Jenkins API. > \[1\] https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/jenkins-script/... > There is this error message in the log: > {code} > ERROR: Build step failed with exception > org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.HashMap > {code} > The rights were limited for a security reason so I need to findout a workaround. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25515) GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25515?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25515. -------------------------------- > GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25515 > URL: https://issues.jboss.org/browse/JBIDE-25515 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.AM3 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.2.Final > > > A lot of installer tests are failing because after last update of Jenkins script \[1\] GetJBDSInstallerLink.groovy hasn't permission to use some features of Jenkins API. > \[1\] https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/jenkins-script/... > There is this error message in the log: > {code} > ERROR: Build step failed with exception > org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.HashMap > {code} > The rights were limited for a security reason so I need to findout a workaround. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4640) Typo in JBoss Developer Studio Installation screen

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4640?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4640: -------------------------------- Story Points: 1 Sprint: devex #143 January 2018 > Typo in JBoss Developer Studio Installation screen > -------------------------------------------------- > > Key: JBDS-4640 > URL: https://issues.jboss.org/browse/JBDS-4640 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.1.0.GA, 11.2.0.AM2 > Reporter: Melissa Flinn > Assignee: Denis Golovin > Priority: Minor > Fix For: 11.2.0.GA > > Attachments: DevStudioInstallScreen_wTypo.png > > > I noticed this issue in a previous GA release and in the latest release from Dec 22 that I just installed on my Lenovo laptop > Red Hat JBoss Developer Studio > Version: 11.2.0.AM3 > Build id: AM3-v20171222-0707-B1813 > Build date: 20171222-0707 > In the Dev Studio Installer - Step 1 of 10 - there is a typo: > Click the "Next" Button to proceed*ed* to the next screen. > "proceeded" should be "proceed" as in: > Click the "Next" Button to proceed to the next screen. > Attached is a screen shot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4640) Typo in JBoss Developer Studio Installation screen

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4640?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4640: ----------------------------------- Assignee: Denis Golovin > Typo in JBoss Developer Studio Installation screen > -------------------------------------------------- > > Key: JBDS-4640 > URL: https://issues.jboss.org/browse/JBDS-4640 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.1.0.GA, 11.2.0.AM2 > Reporter: Melissa Flinn > Assignee: Denis Golovin > Priority: Minor > Fix For: 11.2.0.GA > > Attachments: DevStudioInstallScreen_wTypo.png > > > I noticed this issue in a previous GA release and in the latest release from Dec 22 that I just installed on my Lenovo laptop > Red Hat JBoss Developer Studio > Version: 11.2.0.AM3 > Build id: AM3-v20171222-0707-B1813 > Build date: 20171222-0707 > In the Dev Studio Installer - Step 1 of 10 - there is a typo: > Click the "Next" Button to proceed*ed* to the next screen. > "proceeded" should be "proceed" as in: > Click the "Next" Button to proceed to the next screen. > Attached is a screen shot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4640) Typo in JBoss Developer Studio Installation screen

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4640?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4640: -------------------------------- Fix Version/s: 11.2.0.GA > Typo in JBoss Developer Studio Installation screen > -------------------------------------------------- > > Key: JBDS-4640 > URL: https://issues.jboss.org/browse/JBDS-4640 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.1.0.GA, 11.2.0.AM2 > Reporter: Melissa Flinn > Assignee: Denis Golovin > Priority: Minor > Fix For: 11.2.0.GA > > Attachments: DevStudioInstallScreen_wTypo.png > > > I noticed this issue in a previous GA release and in the latest release from Dec 22 that I just installed on my Lenovo laptop > Red Hat JBoss Developer Studio > Version: 11.2.0.AM3 > Build id: AM3-v20171222-0707-B1813 > Build date: 20171222-0707 > In the Dev Studio Installer - Step 1 of 10 - there is a typo: > Click the "Next" Button to proceed*ed* to the next screen. > "proceeded" should be "proceed" as in: > Click the "Next" Button to proceed to the next screen. > Attached is a screen shot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4640) Typo in JBoss Developer Studio Installation screen

by Melissa Flinn (JIRA)

Melissa Flinn created JBDS-4640: ----------------------------------- Summary: Typo in JBoss Developer Studio Installation screen Key: JBDS-4640 URL: https://issues.jboss.org/browse/JBDS-4640 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: installer Affects Versions: 11.2.0.AM2, 11.1.0.GA Reporter: Melissa Flinn Priority: Minor Attachments: DevStudioInstallScreen_wTypo.png I noticed this issue in a previous GA release and in the latest release from Dec 22 that I just installed on my Lenovo laptop Red Hat JBoss Developer Studio Version: 11.2.0.AM3 Build id: AM3-v20171222-0707-B1813 Build date: 20171222-0707 In the Dev Studio Installer - Step 1 of 10 - there is a typo: Click the "Next" Button to proceed*ed* to the next screen. "proceeded" should be "proceed" as in: Click the "Next" Button to proceed to the next screen. Attached is a screen shot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-563) [RedOx] Goal 2.2 - Manage Plugin

by Lucas Bullen (JIRA)

[ https://issues.jboss.org/browse/ERT-563?page=com.atlassian.jira.plugin.sy... ] Lucas Bullen resolved ERT-563. ------------------------------ Resolution: Done > [RedOx] Goal 2.2 - Manage Plugin > -------------------------------- > > Key: ERT-563 > URL: https://issues.jboss.org/browse/ERT-563 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Lucas Bullen > Assignee: Lucas Bullen > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Manage rustup from the plugin (preference page) - Check whether ~/.rustup and ~/.cargo contain rustup already and make use of it in this case. If not fetch rustup-init and auto install it. One should be able to switch between stable and nightly toolchain. Have rls-preview, rust-src and rust-analysis component installed/updated using rustup -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-564) [RedOx] Goal 2.3 - Wizards

by Lucas Bullen (JIRA)

[ https://issues.jboss.org/browse/ERT-564?page=com.atlassian.jira.plugin.sy... ] Lucas Bullen resolved ERT-564. ------------------------------ Resolution: Done > [RedOx] Goal 2.3 - Wizards > -------------------------- > > Key: ERT-564 > URL: https://issues.jboss.org/browse/ERT-564 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Lucas Bullen > Assignee: Lucas Bullen > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Provide new wizards, launch, export - Cargo (rust build system, which will be provisioned by rustup) provides commands for init (bin or library project), build, package, clean, test, run, rustdoc so all these should be thin layer redirecting to cargo calls -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25545) CDK run via jenkins requires proper ssh to be used on windows slaves

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25545?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25545: ---------------------------------- Sprint: devex #143 January 2018 > CDK run via jenkins requires proper ssh to be used on windows slaves > -------------------------------------------------------------------- > > Key: JBIDE-25545 > URL: https://issues.jboss.org/browse/JBIDE-25545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.Final > Environment: windows, jenkins > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.2.Final > > > When CDK is being run via jenkins on windows slaves, we can see that improper ssh is used to connect to rhel guest, and command that follows will fail: > ie.: > {code} > 14:17:12 &{[-F /dev/null -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none docker(a)127.0.0.1 -o IdentitiesOnly=yes -i C:\Users\Admin\.minishift\machines\minishift\id_rsa -p 49784] C:\ProgramData\chocolatey\bin\ssh.exe <nil>} > 14:17:12 About to run SSH command: > 14:17:12 printf '%s' '-----BEGIN CERTIFICATE----- > 14:17:12 MIICzTCCAbWgAwIBAgIQIo4gxNYty+nXDs+ketnGKDANBgkqhkiG9w0BAQsFADAQ > ... > lwvqfWHvZ3Jo94PygMlhLQTWVMVpXAIBdx8ypeeVyMhcUuPJDa01nhPr3nhMBKPj > 14:17:12 fg== > 14:17:12 -----END CERTIFICATE----- > 14:17:12 ' | sudo tee /etc/docker/ca.pem > 14:17:12 SSH cmd err, output: exit status 1: bash: -c: line 0: unexpected EOF while looking for matching `'' > 14:17:12 bash: -c: line 1: syntax error: unexpected end of file > 14:17:12 > 14:17:14 FAIL E0103 14:17:14.245649 4008 start.go:364] Error starting the VM: Error creating the VM. Error creating machine: Error running provisioning: ssh command error > {code} > This is because CDK will use first ssh on windows path. Fix for this could be position proper ssh (one from cygwin64 installation) on the path beginning. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25545) CDK run via jenkins requires proper ssh to be used on windows slaves

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-25545: ------------------------------------- Summary: CDK run via jenkins requires proper ssh to be used on windows slaves Key: JBIDE-25545 URL: https://issues.jboss.org/browse/JBIDE-25545 Project: Tools (JBoss Tools) Issue Type: Bug Components: qa Affects Versions: 4.5.2.Final Environment: windows, jenkins Reporter: Ondrej Dockal Assignee: Ondrej Dockal Priority: Critical Fix For: 4.5.2.Final When CDK is being run via jenkins on windows slaves, we can see that improper ssh is used to connect to rhel guest, and command that follows will fail: ie.: {code} 14:17:12 &{[-F /dev/null -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none docker(a)127.0.0.1 -o IdentitiesOnly=yes -i C:\Users\Admin\.minishift\machines\minishift\id_rsa -p 49784] C:\ProgramData\chocolatey\bin\ssh.exe <nil>} 14:17:12 About to run SSH command: 14:17:12 printf '%s' '-----BEGIN CERTIFICATE----- 14:17:12 MIICzTCCAbWgAwIBAgIQIo4gxNYty+nXDs+ketnGKDANBgkqhkiG9w0BAQsFADAQ ... lwvqfWHvZ3Jo94PygMlhLQTWVMVpXAIBdx8ypeeVyMhcUuPJDa01nhPr3nhMBKPj 14:17:12 fg== 14:17:12 -----END CERTIFICATE----- 14:17:12 ' | sudo tee /etc/docker/ca.pem 14:17:12 SSH cmd err, output: exit status 1: bash: -c: line 0: unexpected EOF while looking for matching `'' 14:17:12 bash: -c: line 1: syntax error: unexpected end of file 14:17:12 14:17:14 FAIL E0103 14:17:14.245649 4008 start.go:364] Error starting the VM: Error creating the VM. Error creating machine: Error running provisioning: ssh command error {code} This is because CDK will use first ssh on windows path. Fix for this could be position proper ssh (one from cygwin64 installation) on the path beginning. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2018