[JBoss JIRA] (JBIDE-26170) Define JAVAxx and OPENJDKxx for new JDKs and OpenJDKs installed
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26170?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-26170.
-----------------------------------
Resolution: Done
Resolving this issue. The linked ticket is now closed. Feel free to open a new issue or ticket if some of the jdks still don't work.
> Define JAVAxx and OPENJDKxx for new JDKs and OpenJDKs installed
> ---------------------------------------------------------------
>
> Key: JBIDE-26170
> URL: https://issues.jboss.org/browse/JBIDE-26170
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.6.0.Final
> Reporter: Jeff MAURY
> Assignee: Martin Malina
> Fix For: 4.9.0.AM3
>
> Attachments: jdk_paths.png, jdk_vars.png
>
>
> The JBoss Tools JDK9+ jobs rely on JAVAxx and OPENJDKxx variables through the toolchains.xml file. As we want to move those jobs to Java10 and Java11, we need those variables to be defined
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (JBIDE-26313) checkUnresolvedIssues.py no longer works with latest python or latest JIRA release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26313?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-26313.
------------------------------
> checkUnresolvedIssues.py no longer works with latest python or latest JIRA release
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-26313
> URL: https://issues.jboss.org/browse/JBIDE-26313
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM2
>
>
> A couple months ago, I could run this script and it would automatically move JIRAs from last sprint to next sprint.
> {code}
> export userpass=JIRAUSER:JIRAPWD
> # can filter out labels using --skipLabels "releasework, task, qa" etc.
> # can do a dry run (list issues, do not change them) with -D
> # skip verifying JIRA fixversions with -S
> # automatically apply changes with -A
> # for the latest sprint names see agile board https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=641&view=planning
> # sometimes the sprint_NEXT is already created, but with a name that's different from what you might expect (eg., different month, wrong year)
> # if previous sprint is done, use sprint=sprint_NEXT here
> sprint="devex #153 August 2018"
> sprint_NEXT="devex #154 September 2018"
> versionWithRespin_jbt=4.9.0.AM2
> versionWithRespin_jbt_NEXT=4.9.0.AM3
> versionWithRespin_ds=12.9.0.AM2
> versionWithRespin_ds_NEXT=12.9.0.AM3
> python -W ignore /tmp/jbt.github/jbosstools-build-ci/util/checkUnresolvedIssues.py -S --jira https://issues.jboss.org \
> --jbt ${versionWithRespin_jbt} --jbt_NEXT ${versionWithRespin_jbt_NEXT} \
> --ds ${versionWithRespin_ds} --ds_NEXT ${versionWithRespin_ds_NEXT} \
> --sprint "${sprint}" --sprint_NEXT "${sprint_NEXT}" --skipLabels "task, releasework" -A
> {code}
> Now it's broken because ...? not sure. Problem happens on line 191.
> {code}
> Traceback (most recent call last):
> File "/tmp/jbt.github/jbosstools-build-ci/util/checkUnresolvedIssues.py", line 191, in <module>
> updateIssues(components.getIssuesFromQuery(query, jiraserver, jirauser, jirapwd), True, \
> File "/home/nboldt/tru/jbosstools-build-ci/util/components.py", line 196, in getIssuesFromQuery
> return doQuery(query, 'item', jiraserver, jirauser, jirapwd, 1000)
> File "/home/nboldt/tru/jbosstools-build-ci/util/components.py", line 215, in doQuery
> xml = minidom.parseString(q.text)
> File "/usr/lib64/python2.7/xml/dom/minidom.py", line 1928, in parseString
> return expatbuilder.parseString(string)
> File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 940, in parseString
> return builder.parseString(string)
> File "/usr/lib64/python2.7/xml/dom/expatbuilder.py", line 223, in parseString
> parser.Parse(string, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\ufffd' in position 172594: ordinal not in range(128)
> {code}
> Seems to be a problem with `xml = minidom.parseString(q.text)` on line 215 of components.py
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months
[JBoss JIRA] (JBIDE-26323) Seems we missed 4.9.0.AM1
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-26323:
----------------------------------
Summary: Seems we missed 4.9.0.AM1
Key: JBIDE-26323
URL: https://issues.jboss.org/browse/JBIDE-26323
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: website
Affects Versions: 4.9.0.AM1
Reporter: Jeff MAURY
Assignee: Nick Boldt
Fix For: 4.9.0.AM3
I noticed 4.9.0.AM1 was not defined in website causing this release to appear as 'Coming soon' even after 4.9.0.AM2 is out.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 10 months