-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-54133] Encode console notes on master for JEP-210 compatibility #32
Conversation
…e them safe for JEP-210.
There is a timeout in |
Weirdness. With |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix here looks good to me, although I think it would be good to update related documentation as described in jenkinsci/workflow-durable-task-step-plugin#80 (comment).
<jenkins.version>1.651.3</jenkins.version> | ||
<revision>1.9</revision> | ||
<changelist>-SNAPSHOT</changelist> | ||
<jenkins.version>2.121.2</jenkins.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Big jump, but required for JEP-210 compatibility. Based on these usage stats, around 73% of users of ant 1.8 are on Jenkins 2.121.2 or newer anyway, so this seems fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyway even if there is some unrelated fix we realize we need to deliver urgently to the remaining 27%, it is easy enough to publish a backport.
JENKINS-54133: As opposed to the general case in jenkinsci/workflow-durable-task-step-plugin#80, in this case it is easy enough to be compatible with JEP-210. Test deps are on jenkinsci/durable-task-plugin#86 + jenkinsci/workflow-durable-task-step-plugin#87.