I once was a Siebel expert...
I once was a Siebel expert, with its demise came a challenge for me.
I am happy I had to let it go, it opened amazing new possiblities for me.
Today I donated the last of these books.
Home of Shariq Mustaquim on the Internet!
I once was a Siebel expert, with its demise came a challenge for me.
I am happy I had to let it go, it opened amazing new possiblities for me.
Today I donated the last of these books.
Picture them in Amazon!!!
Templates for abrupt absence from Office. Copy/Paste
A lot of customers ask:
Can a CodePipeline GitHub source provide more than just one branch?
CodePipeline can currently only run on a single branch per source action which is defined in the action configuration. You need to specify a git repository and branch name when you create a pipeline, so if a branch name is unknown like GitFlow branching model, it is not possible to create a pipeline in advance.
CodePipeline tied to a single git branch is more of a feature of CodePipeline as the design is more inclined towards Trunk based development. Also, as per the designers of this service, CodePipeline is designed for post-merge/release validation. That is, once your change is ready to be released to production and is merged into your master/main branch, CodePipeline takes over and automatically tests and releases the final merged set of changes. CodePipeline has a lot of features like stage locking, superseding versions, etc. which don't work well for the case where you want to test a change in isolation before it's merged (e.g. feature branch testing or pull request testing.) Therefore there currently isn't a recommended way to do this in CodePipeline.
Gave a training to fellow Amazonians on Jenkins.
I setup a GitHub repo to create the necessary Infrastructure: https://github.com/shariqmus/intro_to_jenkins
epoch_to_human_time.sh
#!/bin/bash
TD=$(echo $1 | cut -c -10)
gdate -d @$TD