New release

[jenkinsci]

New release

[thomas-dee]

@JohnStratoudakis The release is planned for the end of this month (January 2019). I'm thinking about releasing a beta version first so that you (and all others) can test that major overhaul.

[prolificcoder]

Alright scratch my comment above, figured out how to trick confluence by using Markup in jenkins and encoding variable names ${duration} to %24%7Bduration%7D.
Also in confluence I am doing insert markup (not confluence wiki)

[JohnStratoudakis]

Hi, when is the expected release date?

And how can I contribute? Any specific list of issues, bugs, or testing that needs to be done?

[thomas-dee]

I just released v2.0-beta1. Please see here on how to install it.

[thomas-dee]

If there are no issues with this beta1 or there is no feedback I will release the final v2.0 at the end of January.

So it would be nice if you'd give some feedback.

[prolificcoder]

Hello, I just started using this beta and it is looking promising.

I am trying embed the status of the build into confluence and the custom text and custom status with
?subject=Custom Text&status=My passing text worked for me

But when I try to use the variables like (${displayName}) in subject, confluence is panicking and just showing wiki markup, I get
Unknown macro: {displayName}

Also i get a similar error when trying to use the branch selector with :${params.BRANCH=master}

Is it something that we have to ask confluence folks? An example of where you are all using these parameters would be great. (is it GitHub only?)

BTW, thanks for working on this, it looks outdated and your initiative is bringing back more use cases.

[prolificcoder]

Actually I experimented with the same in GitHub.com (private instance) and got the desired result

using something like
buildStatus/icon?job=repo%2Fdev&subject=Dev%20build%20duration%20${duration}

Looks like its a problem on confluence side

[thomas-dee]

@prolificcoder Thank you for the feedback. Have you any suggestions for a documentation about this?

[prolificcoder]

i created a medium post about it https://medium.com/mobile-testing/using-jenkins-embeddable-build-plugin-to-spruce-up-confluence-and-github-f7e1090ddfe0
May be you can add an example for confluence in Readme.md?

[prolificcoder]

@thomas-dee I was trying to make use of this plugin to publish code coverage numbers, which I already have as jenkins variable in Jenkinsfile. Is there a way for doing this?

I was looking at DSL and addEmbeddableBadgeConfiguration but do we need provide it with a build id? what is it going to be? That's the part not entirely clear to me.
Also in your documentation i see that you got the build badges based on this configuration but not clear on should we add something Readme.md to make that possible?

[thomas-dee]

No, you do not need to provide a build id. The id argument for addEmbeddableBadgeConfiguration is any unique id you can later reference using the buildStatus/icon?config=<id> customization.

[prolificcoder]

Hmm.. I am trying like you mentioned but it doesn't seem to have any affect on the badge that is showing up in readme.md
My Jenkinsfile looks like this..

and I was expecting the subject to be updated with an eventual desire of showing code coverage numbers dynamically but the subject is defaulting to the hard code build

is there a way to add some more debug to addEmbeddableBadgeConfiguration ? I see one reference of it in Jenkinsfile when I added the configuration but updates seem to have no affect.

[thomas-dee]

Hmm.. I am trying like you mentioned but it doesn't seem to have any affect on the badge that is showing up in readme.md ...

@prolificcoder What does your badge url look like?

_{Sent with GitHawk}

[thomas-dee]

You need to reference the badge configuration using the id androidBuildBadge as config query parameter:

E.g.: http://<jenkins-root-url>/.../badge/icon?config=androidBuildBadge

[prolificcoder]

https://jenkins.go.int.godaddy.com/buildStatus/icon?config=androidBuildBadge

[thomas-dee]

The config parameter references a badge configuration in terms of appearance not in terms of build selection.

If you use the unprotected URL (.../buildStatus/icon?...) you need to select the specific build via the job and build parameters. Please see README.md on how to use them.

https://jenkins.go.int.godaddy.com/buildStatus/icon?job=...&build=...&config=androidBuildBadge

[ajaybgupta]

Any update on the release? It was supposed to be done by 14 Feb 2019.

[thomas-dee]

Any update on the release? It was supposed to be done by 14 Feb 2019.

@ajaybgupta Sorry. The next „flu release“ cropped up. I guess the release will happen next week.

_{Sent with GitHawk}

[ajaybgupta]

Thanks @thomas-dee for the information.

[thomas-dee]

v2.0 released