release-flow | Semantic release versioning with git-flow and composer | BPM library

by bonndan PHP Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | release-flow Summary

release-flow is a PHP library typically used in Automation, BPM applications. release-flow has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

Semantic release versioning with git-flow and composer

Support

Quality

Security

License

Reuse

Support

release-flow has a low active ecosystem.

It has 4 star(s) with 0 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

There are 2 open issues and 0 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of release-flow is current.

Quality

release-flow has 0 bugs and 0 code smells.

Security

release-flow has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

release-flow code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

release-flow does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

release-flow releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi has reviewed release-flow and discovered the below as its top functions. This is intended to give you an instant insight into release-flow implemented functionality, and help decide if they suit your requirements.

Format a JSON string .
Execute a git command .
Update the current version .
Ensure the dependencies .
Get difference type
Detects the version in the current branch .
Check the version of the composer file .
Verifies whether the given string contains the expected output .
Set the release flow dependencies .
Update the composer file version .

Get all kandi verified functions for this library.

release-flow Key Features

No Key Features are available at this moment for release-flow.

release-flow Examples and Code Snippets

No Code Snippets are available at this moment for release-flow.

Community Discussions

Trending Discussions on release-flow

Azure DevOps - Release Pipeline using Deployment Groups or Deployment Job to an Environment?

How to automatically trigger a build for a new branch with wildcard included branch and using path filters?

Azure DevOps pipeline trigger does not fire

QUESTION

Azure DevOps - Release Pipeline using Deployment Groups or Deployment Job to an Environment?

Asked 2020-Nov-16 at 15:37

I'm new-ish to Azure DevOps, so I've missed how it got to where it is. By that I mean that I've seen two different approaches for deployment to environments and I'm not sure which superseded which:

Using a Release Pipeline and Defined Deployment Groups to deploy across stages (environments) See here
Using a Deployment Job in a Pipeline, then using a release pipeline to orchestrate pushing it to different environments - See here

It's interesting that the first link MS docs refer to as being classic, however the latter is not.

I'm currently using Deployment Groups to define the App Servers I deploy to for each environment - then each stage in my Release pipeline targets a different deployment group (environment). This seems the most fluent and natural of the solutions. However, it niggles me that the Environments I setup in the Environments section still maintain that they have never been deployed to - but the deployment groups have recorded the deployments as I expect. Also, the environments allow me to set useful stuff like "business hours" to wake the environment machines.

I looked and tried out some of the approach in the second link I posted - however, this just didn't seem intuative to me - and I can't find much in the DevOps docs to support this approach. I can see the benefits in that you can store your deployment pipeline as code in your repo, and that you have finer controller over the whole process - but I couldn't get variables from the library to be used in any of the replace variables steps or really understand where the release pipelines fit in.

So, I guess I after an inkling of what "best practice" is in this fairly straight forward scenario. I wondering if it's a blend of the two, but to be honest - I'm a bit lost.

...

ANSWER

Answered 2020-Nov-16 at 15:37

Release pipelines and deployment groups have been around for longer than Azure DevOps has been named Azure DevOps. The YAML releases are rather recent. It isn't ever spelled out explicitly, but in my mind it comes down to how you plan on delivering your product.

If you are doing Continuous delivery (choosing when to release, maybe daily, weekly, or quarterly) then I think you must use release pipelines. You might choose this also if you have multiple environments that maybe aren't in the path to production that would want to deploy.

If you are doing Continuous deployment (every push that passes tests goes to production without any real human intervention), then I imagine you'd choose to use the YAML stages. This is kind of spelled out in your second link as the approach for deploying with "release flow", which is Microsoft's approach for delivering changes for Azure DevOps.

Source https://stackoverflow.com/questions/64860718

QUESTION

How to automatically trigger a build for a new branch with wildcard included branch and using path filters?

Asked 2020-May-13 at 06:39

So say I have two directories, /A/, /B/ and I have two (CI) build pipelines listening on release/*.

These two pipelines have path filters limiting them to build when the respective directory contains changes.

How would I make these build pipelines trigger when I create a new branch, e.g. release/1.7 from master? The pipelines do trigger if I omit the path filters however they do not trigger if I include them, this seems to be a "feature" introduced in https://docs.microsoft.com/en-us/azure/devops/release-notes/2019/sprint-155-update#ci-triggers-for-new-branches

I assume the functionality exists since this workflow is what MS/AzDO do themselves: https://docs.microsoft.com/en-us/azure/devops/learn/devops-at-microsoft/release-flow

Edit: To clarity the question, how do I get back the original behavior of builds triggering when a new branch is created while also using path filters?

...

ANSWER

Answered 2020-May-13 at 06:39

Edit: To clarity the question, how do I get back the original behavior of builds triggering when a new branch is created while also using path filters?

For now the behavior you want is not supported cause that feature has partly been removed for a long time. Normally Azure Devops Service won't roll back to old behavior unless there's big issue with new behavior.

You can check the part of the history about the behavior:

2018: Some members (Issue1is not the only one) posted the feature request in our User Voice forum to remove the old behavior(new branch will trigger CI build) => 2019 July: We made changes to modify the old behavior => 2019 Aug: Some members found the behavior changed

In my opinion, one option(button in web portal) to enable/disable the behavior(whether new branch should trigger CI) could be a good choice if you do want to bring back the behavior.

So the answer to your Edited question is to post a new feature request in our User Voice forum to share your feedback. The product team would consider it seriously if it gets enough votes. Hope it helps :)

Source https://stackoverflow.com/questions/61748377

QUESTION

Azure DevOps pipeline trigger does not fire

Asked 2020-Jan-14 at 15:12

Problem

Azure DevOps has a feature (documented here) to trigger a pipeline on completion from another pipeline. This works fine in a test organization, but it won't work in our main organization. There could be something on the organization, project, repository or even branching level, but I'm currently stuck and any help would be appreciated!

Pipelines

Pipeline Pipeline B should run automatically when pipeline Pipeline A completes.

File pipeline-a.yaml for Pipeline A:

...

ANSWER

Answered 2020-Jan-14 at 15:12

Deleting and re-adding the pipeline did the trick. So keep the YAML file but delete the pipeline and add it again.

The Azure DevOps backend seems to miss a relationship between pipelines now and then.

Source https://stackoverflow.com/questions/59615401

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install release-flow

You can download it from GitHub.
PHP requires the Visual C runtime (CRT). The Microsoft Visual C++ Redistributable for Visual Studio 2019 is suitable for all these PHP versions, see visualstudio.microsoft.com. You MUST download the x86 CRT for PHP x86 builds and the x64 CRT for PHP x64 builds. The CRT installer supports the /quiet and /norestart command-line switches, so you can also script it.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: