November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16140) Investigate usage of Jenkins folder plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16140?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16140: ---------------------------------------- [~maxandersen]: We already have some ability to set up an alternative server. https://github.com/jbdevstudio/jbdevstudio-ci contains the config.xml files for each job that can be pushed to whatever Jenkins server we want (through Jenkins Rest API). File https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/pom-sync.xml shows how we use Nick's mojo to do that without much effot. The coupling to JBoss infra is on the publication part which relies on FileSystem and network assumptions that are only true on jenkins.mw.lab. What I see as a big benefit of Folder over buildchow is that: * It is not generative, and generation is always an additional complex step * it makes the concept of hierarchy and factorization natural in Jenkins I may miss something, but I don't see what are the benefits of buildchow over the Folder plugin. I'd be glad to learn more. > Investigate usage of Jenkins folder plugin > ------------------------------------------ > > Key: JBIDE-16140 > URL: https://issues.jboss.org/browse/JBIDE-16140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > > Cloudbees released their folder plugin, which is about factorizing jobs configuration, as an OSS plugin: http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-sourc... > We should investigate on whether it would help to use to manage JBT/JBDS jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16140) Investigate usage of Jenkins folder plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16140?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16140: ---------------------------------------- Summary: Investigate usage of Jenkins folder plugin (was: Investite usage of Jenkins folder plugin) > Investigate usage of Jenkins folder plugin > ------------------------------------------ > > Key: JBIDE-16140 > URL: https://issues.jboss.org/browse/JBIDE-16140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > > Cloudbees released their folder plugin, which is about factorizing jobs configuration, as an OSS plugin: http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-sourc... > We should investigate on whether it would help to use to manage JBT/JBDS jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16140) Investite usage of Jenkins folder plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16140?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16140: ------------------------------------ Requirements: * Each job has a unique name, github repo & branch, SCM check schedule. * Many jobs override defaults in parent pom to pass in different URLs for composite sites, or parameters for testing. Not all jobs use the same params. * Many jobs use the same target platform versions/URLs. But not all -- discovery build may be generating based on a newer TP than what the rest of the stack is using because it links to the Central TP as well as the JBT/JBDS TP. That job in particular gets updated and respun as part of the release process, so it probably shouldn't be generated from a template. * Links between jobs must exist correctly. Generating a job referencing a downstream job which doesn't yet exist may break the job links. * Buildflow job changes periodically as new component projects are added to or removed from the stack. > Investite usage of Jenkins folder plugin > ---------------------------------------- > > Key: JBIDE-16140 > URL: https://issues.jboss.org/browse/JBIDE-16140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > > Cloudbees released their folder plugin, which is about factorizing jobs configuration, as an OSS plugin: http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-sourc... > We should investigate on whether it would help to use to manage JBT/JBDS jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16140) Investite usage of Jenkins folder plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16140?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16140: --------------------------------------------- Another option is something like https://github.com/maxandersen/buildchow which makes it possible to move the configuration around between jenkins servers (assuming the jobs are not tied to jenkins specific settings) > Investite usage of Jenkins folder plugin > ---------------------------------------- > > Key: JBIDE-16140 > URL: https://issues.jboss.org/browse/JBIDE-16140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > > Cloudbees released their folder plugin, which is about factorizing jobs configuration, as an OSS plugin: http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-sourc... > We should investigate on whether it would help to use to manage JBT/JBDS jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on JBIDE-16133: ---------------------------------------- Yes it's a remote DV 6.0.0 ER4, which would be EAP 6.1 > No indication that management authentication fails > -------------------------------------------------- > > Key: JBIDE-16133 > URL: https://issues.jboss.org/browse/JBIDE-16133 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: server > Reporter: Steven Hawkins > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.1.CR1 > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16133: --------------------------------------------- [~shawkins] what are the exact server you are running here and I assume you are running the server remotely because when running locally username/password is not used ? > No indication that management authentication fails > -------------------------------------------------- > > Key: JBIDE-16133 > URL: https://issues.jboss.org/browse/JBIDE-16133 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: server > Reporter: Steven Hawkins > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.1.CR1 > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on JBIDE-16133: ---------------------------------------- > connection reset by peer logged on server side on every management call That is just a side affect of having an invalid username/password. If you put in the correct management credentials, the console log is clear of those errors. > No indication that management authentication fails > -------------------------------------------------- > > Key: JBIDE-16133 > URL: https://issues.jboss.org/browse/JBIDE-16133 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: server > Reporter: Steven Hawkins > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.1.CR1 > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16133: --------------------------------------------- [~shawkins] and when you actually put in correct username/password does the error logging stop on the server side ? Trying to understand if we are dealing with one or two errors: 1) No indication that management authentication fails 2) connection reset by peer logged on server side on every(?) management call > No indication that management authentication fails > -------------------------------------------------- > > Key: JBIDE-16133 > URL: https://issues.jboss.org/browse/JBIDE-16133 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: server > Reporter: Steven Hawkins > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.1.CR1 > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16133: ---------------------------------------- Priority: Critical (was: Major) > No indication that management authentication fails > -------------------------------------------------- > > Key: JBIDE-16133 > URL: https://issues.jboss.org/browse/JBIDE-16133 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: server > Reporter: Steven Hawkins > Priority: Critical > Fix For: 4.1.1.CR1 > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-16133: ------------------------------------------- Assignee: Max Rydahl Andersen > No indication that management authentication fails > -------------------------------------------------- > > Key: JBIDE-16133 > URL: https://issues.jboss.org/browse/JBIDE-16133 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: server > Reporter: Steven Hawkins > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.CR1 > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 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 November 2013