antongolub
commented
4 years ago @moltar
Could you run this cmd locally?
git pull --tags --force https://[secure]@github.com/org/package-foo.gitJust to exclude broken token case.
Closed moltar closed 4 years ago
antongolub
commented
4 years ago @moltar
Could you run this cmd locally?
git pull --tags --force https://[secure]@github.com/org/package-foo.gitJust to exclude broken token case.
the-glima
commented
4 years ago I'm having the same issue.
Yes, I have the GITHUB_TOKEN env configured. Also, this command works for me:
git pull --tags --force https://[secure]@github.com/org/package-foo.gitUsing in my context, of course.
antongolub
commented
4 years ago @moltar @the-glima No explanation was found in logs above, sorry.
It is necessary to spy on getRepoUrl and getRepo helpers.
Once DEBUG env is set, more details will appear in logs:
if (process.env.DEBUG) {
logger.log('getRepoUrl:')
logger.log('urlFromEnv=', urlFromEnv)
logger.log('urlFromStepOpts=', urlFromStepOpts)
logger.log('urlFromOpts=', urlFromOpts)
logger.log('urlFromPackage', urlFromPackage)
logger.log('url=', url)
}
if (process.env.DEBUG) {
logger.log('getRepo:')
logger.log('repoUrl=', repoUrl)
logger.log('repoName=', repoName)
logger.log('repoDomain=', repoDomain)
logger.log('has token=', !!token)
logger.log('enterprise=', enterprise)
}Everything seems to be ok with the latest semrel and plugins. Here's the public repo example: https://github.com/qiwi/mixin
Verified working config for "enterprise":
GH_URL=https://github.<domain>/api/v3/ GH_TOKEN=<token> yarn release{
"name": "@private-scope/package-name",
"description": "Blah-blah-blah",
"version": "1.0.0",
"files": [
"README.md",
"CHANGELOG.md",
"index.js"
],
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"lint": "echo \"Error: no linter configured\" && exit 1",
"build": "yarn docs",
"docs": "rm -rf docs && mkdir docs && echo 'docs' > docs/DOCS.md",
"release": "semantic-release"
},
"dependencies": {},
"devDependencies": {
"@qiwi/semantic-release-gh-pages-plugin": "^1.15.10",
"@semantic-release/commit-analyzer": "^8.0.1",
"@semantic-release/changelog": "^5.0.1",
"@semantic-release/git": "^9.0.0",
"@semantic-release/github": "^7.0.5",
"@semantic-release/npm": "^7.0.5",
"semantic-release": "^17.0.4"
},
"repository": {
"type": "git",
"url": "https://github.<domain>/space/package-name.git"
},
"publishConfig": {
"registry": "https://npm-registry.<domain>"
},
"release": {
"branch": "master",
"verifyConditions": [
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git",
"@qiwi/semantic-release-gh-pages-plugin"
],
"prepare": [
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git"
],
"publish": [
"@semantic-release/npm",
"@semantic-release/github",
[
"@qiwi/semantic-release-gh-pages-plugin",
{
"enterprise": true
}
]
]
}
}Hope this helps.
antongolub
commented
4 years ago @moltar @the-glima, since 1.16.0 the pulling hook can be disabled by setting pullTagsBranch option to empty string.
antongolub
commented
4 years ago One more similar case. BuildId: https://github.com/microsoft/jacdac-ts/runs/811365079 Commit: https://github.com/microsoft/jacdac-ts/commit/1ba1d9a54aff2a8b025160944ecc626e6d5bb1d8
antongolub
commented
4 years ago @moltar @the-glima @pelikhan @kjens93
We still don't have the stand that reproduces this issue. As an experiment, we've tried to replace the custom url builder with "native" semrel mechanics (#94). Everything seems to be ok on our testing repo travis/354764920, but it isn't clear whether the problem is fixed.
Could anybody try the latest beta? semantic-release-gh-pages-plugin@4.0.0-beta.0 Thanks.
qiwibot
commented
4 years ago :tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
I am getting the following error message.
The GitHub action step is like this (included
GITHUB_TOKEN):Error:
Any ideas?
Thanks!