Triggering a CI/CD build when a tag is added to the GitHub repo this repo is forked from?












2















There's a project using GitHub releases to release their packages. I've built a process that repackages the released files and uploads the repackaged files to a special GitHub release in my fork of the repository.



I'd like to fully automate this by having my process run automatically whenever a new GitHub release tag is added to the original repository.



Is there an existing CI/CD service that could do this?




  • If yes which and can you point me to the right area of the docs to figure it out?

  • If no, are there options for wiring this up myself somehow? For example, using a webhook and an existing service in a non-standard way to accomplish the goal?










share|improve this question




















  • 2





    The repo owner would have to set up a webhook to deliver some service you could subscribe to. Unfortunately the only option would be to poll the API for a new release.

    – osowskit
    Nov 24 '18 at 5:07











  • I feared as much, @osowskit, thanks for confirming!

    – Ross Patterson
    Nov 24 '18 at 19:02


















2















There's a project using GitHub releases to release their packages. I've built a process that repackages the released files and uploads the repackaged files to a special GitHub release in my fork of the repository.



I'd like to fully automate this by having my process run automatically whenever a new GitHub release tag is added to the original repository.



Is there an existing CI/CD service that could do this?




  • If yes which and can you point me to the right area of the docs to figure it out?

  • If no, are there options for wiring this up myself somehow? For example, using a webhook and an existing service in a non-standard way to accomplish the goal?










share|improve this question




















  • 2





    The repo owner would have to set up a webhook to deliver some service you could subscribe to. Unfortunately the only option would be to poll the API for a new release.

    – osowskit
    Nov 24 '18 at 5:07











  • I feared as much, @osowskit, thanks for confirming!

    – Ross Patterson
    Nov 24 '18 at 19:02
















2












2








2


0






There's a project using GitHub releases to release their packages. I've built a process that repackages the released files and uploads the repackaged files to a special GitHub release in my fork of the repository.



I'd like to fully automate this by having my process run automatically whenever a new GitHub release tag is added to the original repository.



Is there an existing CI/CD service that could do this?




  • If yes which and can you point me to the right area of the docs to figure it out?

  • If no, are there options for wiring this up myself somehow? For example, using a webhook and an existing service in a non-standard way to accomplish the goal?










share|improve this question
















There's a project using GitHub releases to release their packages. I've built a process that repackages the released files and uploads the repackaged files to a special GitHub release in my fork of the repository.



I'd like to fully automate this by having my process run automatically whenever a new GitHub release tag is added to the original repository.



Is there an existing CI/CD service that could do this?




  • If yes which and can you point me to the right area of the docs to figure it out?

  • If no, are there options for wiring this up myself somehow? For example, using a webhook and an existing service in a non-standard way to accomplish the goal?







git github continuous-integration continuous-deployment github-release






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 24 '18 at 7:50









CodeWizard

53k127096




53k127096










asked Nov 23 '18 at 21:17









Ross PattersonRoss Patterson

5,0451431




5,0451431








  • 2





    The repo owner would have to set up a webhook to deliver some service you could subscribe to. Unfortunately the only option would be to poll the API for a new release.

    – osowskit
    Nov 24 '18 at 5:07











  • I feared as much, @osowskit, thanks for confirming!

    – Ross Patterson
    Nov 24 '18 at 19:02
















  • 2





    The repo owner would have to set up a webhook to deliver some service you could subscribe to. Unfortunately the only option would be to poll the API for a new release.

    – osowskit
    Nov 24 '18 at 5:07











  • I feared as much, @osowskit, thanks for confirming!

    – Ross Patterson
    Nov 24 '18 at 19:02










2




2





The repo owner would have to set up a webhook to deliver some service you could subscribe to. Unfortunately the only option would be to poll the API for a new release.

– osowskit
Nov 24 '18 at 5:07





The repo owner would have to set up a webhook to deliver some service you could subscribe to. Unfortunately the only option would be to poll the API for a new release.

– osowskit
Nov 24 '18 at 5:07













I feared as much, @osowskit, thanks for confirming!

– Ross Patterson
Nov 24 '18 at 19:02







I feared as much, @osowskit, thanks for confirming!

– Ross Patterson
Nov 24 '18 at 19:02














1 Answer
1






active

oldest

votes


















-1















I'd like to fully automate this by having my process run automatically whenever a new GitHub release tag is added to the original repository.




GitHub has webhooks for this purpose.



https://developer.github.com/v3/activity/events/types/#createevent




CreateEvent

Represents a created repository, branch, or tag.



Note: webhooks will not receive this event for created repositories. Additionally, webhooks will not receive this event for tags if more than three tags are pushed at once.




Once the tag is pushed GitHub will invoke the given URL with the appropriate JSON as described in the DOCs above.






share|improve this answer
























  • Yeah, I read the webhook docs, and to my reading that would only trigger for a creation of a tag in this repository, not the repository it was forked from. Do you know otherwise?

    – Ross Patterson
    Nov 24 '18 at 19:01











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53453027%2ftriggering-a-ci-cd-build-when-a-tag-is-added-to-the-github-repo-this-repo-is-for%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









-1















I'd like to fully automate this by having my process run automatically whenever a new GitHub release tag is added to the original repository.




GitHub has webhooks for this purpose.



https://developer.github.com/v3/activity/events/types/#createevent




CreateEvent

Represents a created repository, branch, or tag.



Note: webhooks will not receive this event for created repositories. Additionally, webhooks will not receive this event for tags if more than three tags are pushed at once.




Once the tag is pushed GitHub will invoke the given URL with the appropriate JSON as described in the DOCs above.






share|improve this answer
























  • Yeah, I read the webhook docs, and to my reading that would only trigger for a creation of a tag in this repository, not the repository it was forked from. Do you know otherwise?

    – Ross Patterson
    Nov 24 '18 at 19:01
















-1















I'd like to fully automate this by having my process run automatically whenever a new GitHub release tag is added to the original repository.




GitHub has webhooks for this purpose.



https://developer.github.com/v3/activity/events/types/#createevent




CreateEvent

Represents a created repository, branch, or tag.



Note: webhooks will not receive this event for created repositories. Additionally, webhooks will not receive this event for tags if more than three tags are pushed at once.




Once the tag is pushed GitHub will invoke the given URL with the appropriate JSON as described in the DOCs above.






share|improve this answer
























  • Yeah, I read the webhook docs, and to my reading that would only trigger for a creation of a tag in this repository, not the repository it was forked from. Do you know otherwise?

    – Ross Patterson
    Nov 24 '18 at 19:01














-1












-1








-1








I'd like to fully automate this by having my process run automatically whenever a new GitHub release tag is added to the original repository.




GitHub has webhooks for this purpose.



https://developer.github.com/v3/activity/events/types/#createevent




CreateEvent

Represents a created repository, branch, or tag.



Note: webhooks will not receive this event for created repositories. Additionally, webhooks will not receive this event for tags if more than three tags are pushed at once.




Once the tag is pushed GitHub will invoke the given URL with the appropriate JSON as described in the DOCs above.






share|improve this answer














I'd like to fully automate this by having my process run automatically whenever a new GitHub release tag is added to the original repository.




GitHub has webhooks for this purpose.



https://developer.github.com/v3/activity/events/types/#createevent




CreateEvent

Represents a created repository, branch, or tag.



Note: webhooks will not receive this event for created repositories. Additionally, webhooks will not receive this event for tags if more than three tags are pushed at once.




Once the tag is pushed GitHub will invoke the given URL with the appropriate JSON as described in the DOCs above.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 24 '18 at 7:54









CodeWizardCodeWizard

53k127096




53k127096













  • Yeah, I read the webhook docs, and to my reading that would only trigger for a creation of a tag in this repository, not the repository it was forked from. Do you know otherwise?

    – Ross Patterson
    Nov 24 '18 at 19:01



















  • Yeah, I read the webhook docs, and to my reading that would only trigger for a creation of a tag in this repository, not the repository it was forked from. Do you know otherwise?

    – Ross Patterson
    Nov 24 '18 at 19:01

















Yeah, I read the webhook docs, and to my reading that would only trigger for a creation of a tag in this repository, not the repository it was forked from. Do you know otherwise?

– Ross Patterson
Nov 24 '18 at 19:01





Yeah, I read the webhook docs, and to my reading that would only trigger for a creation of a tag in this repository, not the repository it was forked from. Do you know otherwise?

– Ross Patterson
Nov 24 '18 at 19:01




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53453027%2ftriggering-a-ci-cd-build-when-a-tag-is-added-to-the-github-repo-this-repo-is-for%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Create new schema in PostgreSQL using DBeaver

Deepest pit of an array with Javascript: test on Codility

Costa Masnaga