Closed secustor closed 1 month ago
Hi there,
You're asking us to support a new package manager. We need to know some basic information about this package manager first. Please copy/paste the new package manager questionnaire, and fill it out in full.
Once the questionnaire is filled out we'll decide if we want to support this new manager.
Good luck,
The Renovate team
@ubiratansoares As discussed, could you fill out the questionnaire? Thx!
@secustor On my list! 🔥
@secustor : Let me know if I missed anything!
Did you read our documentation on adding a package manager?
Mainly one YAML file called by bitrise.yml. A working example can be found on this DuckDuckGo fork
The most suitable to match exactly
bitrise.y(a)ml at root folder
Several options may work here
SemVer (Major.Minor.Patch)
^1.0.0
or 1.x
?^1.0.0
or 1.x
)We may need a new data source since we have two options for getting CI steps and their respective versions. It'll depend on how we want to crawl data about Bitrise Steps.
We have the collection of Bitrise Steps aggregated (automatically) in a mono-repo maintained by Bitrise, from where we can get all step names and all available versions for each step on top of folder/path parsing. If I'm not missing anything, a new Data Source might be required here. The advantage of implementing this option is getting all steps + versions in a single Git clone or single API call to get the latest archive for the main branch
We also have the Github organization where Bitrise hosts all source code for all steps collected in the mono-repo mentioned above. In this case, each repository matches a CI step and a Github Release / Github Tag is available for each step, which means we don't need these two Data Sources, but we eventually have to loop for all repos on that organization
NOTE the naming is not consistent some are prefixed with bitrise-step-
other are step-
.
I don't think so, but happy to go for anything that's missing!
:tada: This issue has been resolved in version 38.7.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
What would you like Renovate to be able to do?
Bitrise is a platform which provides CI services for mobile apps.
Bitrise uses step definitions which are defined in yaml files with the name
bitrise.yaml
.Users of Bitrise are:
If you have any ideas on how this should be implemented, please tell us here.
Steps are hosted and managed by repos with following pattern:
https://github.com/bitrise-steplib/steps-{{step reference}}
.Should result in a dependency with
github-release
datasource andbitrise-steplib/steps-script
aspackageName
.If
default_step_lib_source
deviates fromhttps://github.com/bitrise-io/bitrise-steplib.git
,skipReason
should be set as we have no datasource to extract the folders in a generic way.Is this a feature you are interested in implementing yourself?
Maybe