Monica Shiralkar

Ranch Hand
+ Follow
since Jul 07, 2012
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
13
In last 30 days
0
Total given
0
Likes
Total received
33
Received in last 30 days
0
Total given
391
Given in last 30 days
1
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Monica Shiralkar

Stephan van Hulst wrote:
The only thing I can tell you for sure is that the pipeline first builds, then deploys.



But isn't that the only possible obvious order as you need to first build something in order to deploy it?

Stephan van Hulst wrote:

Testing the software can be done as part of the build by the build tool, or it can be a separate step in the CI pipeline, or it can even be done at the very end after the software has been deployed, or any combination of the above. It completely depends on the team philosophy and on the project requirements.



But if testing is done at the very end after the software has been deployed, then is it not a waste in some cases to even proceed if the test cases fail?
If the test cases fail, then shouldn't, it be not allowed to proceed to deploy and this should be the obvious order?
1 week ago

Tim Holloway wrote:

Jenkins can do a lot of its magic directly, but it also leverages the tools it controls. For example, if a Maven build includes the "test" goal, that's what causes the tests to be run using the test runner Maven plugin and can cause them to be summarized and reported via the surefire-reports plugin.


Thanks. I understood this now.
1 week ago
We have Jenkins pipeline in our project. I too push changes to our repo and run programs after those deploy but Jenkins pipeline has been a Blackbox for me. So instead of continuing to remain confused about what it does I thought of breaking what it does into parts. Although I don't know it fully, what I have understood far is that broadly it is doing 3 things for us: running test cases and if the test cases pass creates the build artifacts and then deploy it to cloud (using spinnaker).
1 week ago
CICD can have multiple steps in the pipeline but broadly are creating the build artifacts, running test cases and deploying the build artifacts, typically the 3 main parts of CICD pipeline ? Thanks
2 weeks ago

Mike Simmons wrote:It means to pay attention (attend) to vocal modulations, how speaker's voices change as they talk, changes in pitch, volume, speed, and possibly other things.



Ok. On a level good speakers may speak most of the words normally and slightly modify tone/pitch/volume for the words that they wasn't to emphasize ?
1 month ago

Stephan van Hulst wrote:No, because it's common courtesy not to waste your colleagues' time with a pull request that contains merge conflicts from the very instant it was created.

Be courteous, and fix merge conflicts before you create the pull request.



Do you mean to not waste the time of the collegues who are approvers of the PR? Yes, should not do that.  I think my PR would affect only me and the approved. But there may be some scenario where it may affect others so and ofcourse their time should not be wasted.
1 month ago

Stephan van Hulst wrote:No, because it's common courtesy not to waste your colleagues' time with a pull request that contains merge conflicts from the very instant it was created.

Be courteous, and fix merge conflicts before you create the pull request.



Do you mean to not waste the time of the collegues who are approvers of the PR? Yes, should not do that.
1 month ago

Tim Holloway wrote:
And of course, do so judiciously. Overdo it and people won't take you seriously.



Thanks. Understood that one has to know how much to do and not over do.

Tim Holloway wrote:

So you first must attend to normal modulations,



What does attending normal modulations mean
1 month ago

Les Morgan wrote:

A good speaker knows how and when to emphasis using slight tonal modulation of their voice, or slight volume changes.  Think of a good speaker, one you enjoy listening too.  listen for how they emphasize and contrast things using voice inflections.

nobody likes to listen to a monotone presentation, but no body like to listen to a person that is inappropriately using voice inflections or volume in their voice either.

Les



Thanks. I always spoke in monotone way. I will try to learn how to emphasize and contrast things using voice inflections.
1 month ago
During verbal communication, one can communicate normally or using voice modulation.  Is using voice modulation during verbal communication a better way of speaking?
1 month ago

Stephan van Hulst wrote:
When the feature is done, pull the target branch. This should NEVER lead to merge conflicts.
Merge the target branch into your feature branch locally.
Merging the target branch into the feature branch may lead to merge conflicts. Resolve these.



This is exactly where the confusion is. There were times when after the feature was done, instead of pulling the target branch and merging, I directly pushed the code and created the PR. On creating the PR it showed "cannot be merged due to conflicts", then I pulled from the target and merged and resolved it.
So, shouldn't instead of always pulling the target each time after the feature is done, better the create the PR and only if it shows conflicts, then only pull the target and merge and resolve.?
1 month ago

Stephan van Hulst wrote:Jenkins is NOT a tool that takes care of CI/CD completely. It's a tool that manages the CI/CD pipeline. It delegates to other tools for the specifics of CI or CD.


Thanks. Understood.


Stephan van Hulst wrote:

Depending on your requirements, CodeDeploy is an example of a tool you can use to deploy your application



And in case of deploying not on cloud but on web servers ike Tomcat, what are the commonly used tools which Jenkins typically delegates to ?
1 month ago
Is it so that although Jenkins is a tool that can take care of compete CICD, when it comes to cloud the better way is to use Jenkins only for CI part and do CD part using a Cloud CD tools like CodeDeploy or Spinnaker ?
1 month ago
Thanks. So, if we are using Jenkins with say CodeDeploy/Spinnaker or some other tool, then when Jenkins pipeline gets triggered by the code check and runs the test case and creates the deployable artefacts, then whatever part CodeDeploy/Spinnaker or other tool is doing by making it easy to deploy, broadly what is the way to be followed it would have been without them ?
1 month ago