Skip to content
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

build.link shows commit, not build #73

Open
sebphi opened this issue Apr 12, 2023 · 0 comments
Open

build.link shows commit, not build #73

sebphi opened this issue Apr 12, 2023 · 0 comments

Comments

@sebphi
Copy link

sebphi commented Apr 12, 2023

Hi! Sorry in advance if this is not the right place.

We use drone-email successfully with woodpecker (replacement for drone) and the email which is sent on e.g. failure contains a link to the commit that supposedly caused the failure. However, the email text says Failed build #xxx and it would make more sense to me if the link actually lead to the build (often enough, it's not the commit causing the fail, but something else in our build chain).

If i see that right, the template uses build.link and that is set by the environment variable DRONE_BUILD_LINK which already contains the erroneous link (found out by an echo command in a build step). Is there something that can be done within the notify step to set DRONE_BUILD_LINK to the proper value? Here is what that step looks like atm:

  notify:
    image: docker-proxy/drillster/drone-email
    pull: true
    settings:
      host: mail.domain
      from: woodpecker@domain
      username: mailsender
      password:
        from_secret: email_password
      recipients:
      - woodpecker@domain
      starttls: true
    when:
      event: [push, pull_request]
      status:
      - failure
      - success

I have tried commands and environment so far, to no avail.

Or is this something which would need to be fixed in woodpecker (or somewhere else)?

Thanks in advance,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant