-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
CI publish error #1183
Comments
It means that your release is already published and not a prerelease or draft . Is it not true? |
It is true, the release is already published. But publishing the release causes a build to happen -- I figured it would be better to say "A release is already published" vs throwing errors, if this is the desired behavior then the issue can be closed. This issue was more of a usability concern. Like I said though, appveyor rebuilds on tag but doesn't throw errors. |
Got your point. You are right. |
Is time check on CI was correct? Was it really two hours ago? |
If you use github to create tags, you can exclude tag branches — https://github.com/develar/onshape-desktop-shell/blob/master/.travis.yml#L42 |
The time check is sometimes 2+ hours - 1 day, it's the first time the publish was drafted -- not updated. Did I misunderstand the suggested workflow? And ah! I'll add that tag clause to prevent rebuilds. |
Following the suggested workflow results in a nasty CI error. This happens once you release the version on github and triggers a rebuild.
This only happens on travis; appveyor is fine.
The text was updated successfully, but these errors were encountered: