I'm looking at the PhoneGap documentation on including plugins into your PhoneGap Build, but InAppPurchaseManager is not there. How can I include it?
Thanks.
I think you should contact them directly via special mailing list below. The mailing list is very active, the team is watching it so they will come back to you shortly.
callback-dev#incubator.apache.org
As per official information it is not possible at present time.
Right now, you cannot submit your own plugins to PhoneGap Build and have them included on our system. We are working on the infrastructure changes to allow this support
Related
I am investigating a way to automate some of our build processes using Jenkins and HPQC. Currently, we have a process where, once a change to fix a defect has been checked in we set its status to "Fixed" and then reassign defect in HPQC from the individual developers to a team lead.
The team lead is tasked with manually deploying a build for the deliverable to the test environment and when he does this he will then update all of the defects assigned to him this way reassigning them to the test lead, who can assign them to individual testers.
I would like to automate this process where I can. Does HPQC have a web API of some kind? So that a remote system (such as a Jenkins build server) could run a post-build action script to gather a bunch of defect numbers (those included in the build) find each defect in HPQC and then update its status and owner?
There is a REST API for ALM / Quality Center, info is accessible:
http://support.openview.hp.com/selfsolve/manuals
You will have to sign up for an account with HP to access it. Ugh, troglodytes.
Search for "ALM REST API", download and read the newest guide and reference for your version of QC.
(We also use QC at my work. It's pretty damn bad. I should try and convince them to get or build something better.)
The answer above is a good one, I found the reference he mentions, but making use of that is not very intuitive, probably because I am such a newb. For my fellow unenlightened you might want to use another reference I found for how to use the reference :
http://www.consulting-bolte.de/index.php/22-hp-alm/hp-alm-rest-api/115-connect-to-hp-alm-via-java-using-rest-api
The key piece of information for me was that inside all of these class files they give you in the "Example Applications" folder there is a reference to a package :
package org.hp.qc.web.restapi.docexamples.docexamples.infrastructure;
This is just another name for all the files located in the guide in the "infrastructure" subfolder. You do not need to go find this out on github or something.
Normally newer verisons of Appdynamics should display windows services if you add them specificially into the config.xml. I did that, restartet the services and the agent, but nothing happened.
Did anyone manage to display the Services ? If yes, where do they appear?
It is a bit hard to completely answer your question and solve the issue with the provided information. However, I hope my questions below help you to get on the right track.
1.) After making the configuration change, did you also restart the AppDynamics.AgentCoordinator_WindowsService? Without restarting it the new configuration will not be applied to the agent itself.
2.) Also important is your windows service hosting any OOTB support entry point like WCF, ASP.NET MVC4 WebAPI, web services etc.? If not, you need to setup a custom entry point. If you check out the AppDynamics documentation and search for'POCO Entry Points' you should get onto the right track
3.) In case No.1 & No.2 did not do the trick, could you please attach the config.xml file for review? Or directly reach out to the AppDynamics customer success team.
Kind regards,
Theo
Disclaimer: I work for AppDynamics as part of the Customer Success team.
Just to add to you answer and to clarify a little. Until release 3.7.7 the .NET agent from AppDynamics used the web.config (for IIS based application), App.config for standalone and windows services or the global.config plus some environment variables to configure the agent.
With the 3.7.8 or later release we replaced this with a cleaner truly singly configuration file approach. The configuration file is called config.xml and located in the %ProgramData%\AppDynamics... directory. For any version after 3.7.8 all settings have to be in the config.xml.
You really should take this up with AppDynamics support by filing a ticket or posting in the support forums... http://www.appdynamics.com/support/#helptab
I would like to have an easy way to add gerrit codes changes with bug reference to the relevant mantis bug.
I have seen some nice example here
But the use an old php scripts that's not part of mantis anymore and seems to be replaced by the source-intergration plugin that you need to configure for every single project you have. I am looking at adding this for lot's of projects. I rather just copy a hook script in the hook folder for all projects.
Versions:
Gerrit 2.7
MantisBT 1.2.15
No ready solution so I created my own plugin extending the source-integration plugin. Let's see if my boss allows me to contribute this as part of the source-integration plugin.
It seems that all of the initial Google results for "using subversion with xcode" are actually just tutorials for installing and configuring svn and Xcode, as opposed to actually using the two (i.e. interacting with svn via Xcode's GUI).
Is anyone aware of a good guide that teaches the tricks and pitfalls of working with svn via Xcode's GUI? Something that bridges the gap between the most excellent Version Control with Subversion book and the Xcode IDE (as in pure Xcode GUI without any terminal command use)?
Edit:
We all love our terminal commands, and we all love Eclipse but (and I mean this in the nicest possible way) neither is really the point of the question. I’d prefer to use svn via Xcode’s IDE instead of via terminal just as I prefer (well, for this case) to code in Xcode’s IDE instead of using vim and gcc. Apple engineers spent a good bit of time implementing that SCM menu in Xcode; someone has to have seen a usage guide somewhere.
I used this page as a reference for setting up my XCode projects with SVN. It is a good starting point, but I'll give a short walkthrough of what I did (since the page isn't really all that helpful!).
A couple notes: I'm using XCode 3.1.2 and Subversion 1.4.2. I've heard of problems with using SVN 1.5, but there are ways around that which I wont get into.
First off, I had a repository already set up and created the XCode project afterwards.
In XCode you need to set it up to know about your repository using the SCM tab in the preferences window. Enter:
A Name (this is arbitrary and used for reference with XCode)
The scheme (http or svn)
The host (i.e. svn.example.com)
The path (the exact path to the SVN repository located on the host)
The port (only if it isn't the default)
And a username and password used to access the repository.
The URL will be auto-filled as you enter the other fields. Hit "OK" when all the fields are good and XCode says it can connect.
Then open your project and do a "Get Info" (Round blue icon with an exclamation mark) on the project itself. Under the "General" tab down at the bottom is an option for SCM, select the repository you made in 1 and close the window.
Now open SCM in the menu-bar and go to "Repositories." Hopefully you've built your repository right using branches, trunk, and other directories at the base level because XCode doesn't have support for checking out the root directory. So go one directory at a time down the list and click the "Checkout" button and select a directory to check it out to (I recommend a "Code" or "Source" or "SVN" directory inside your XCode project directory). You cannot checkout multiple directories at once, but you can tell the next directory to checkout before the first has finished and XCode with queue the commands.
Once that is all done go back to your XCode project window and "Add -> Existing Files..." to your project. Select the directory you've checked out the repository to and I recommend using the "Create folder references" option instead of the "Recursively create groups" option because added and removed items will be automatically reflected in a Folder Reference but not in a Group.
Now you've imported your SVN repository into an XCode project. From here any time you make a change, simply Right-Click (Control-Click if you only have 1 button) in the file and at the bottom of the context menu are the SCM options for comparing, committing, updating, and discarding (reverting) the file. You can also use the SCM menu in the menubar for file or project-wide updates/commits/reverts.
I second the comment by the_mandrill, SVN support from within XCode is very limited, especially if you're used to Eclipse.
I also don't understand why everyone seems to need visual clients. I keep a terminal window open on my project directory and I have no problems interacting with SVN from the command line.
I know this is not quite what you asked, but I wouldn't rely much on the use of SVN from Xcode as what you can do with it is very limited. It's useful for being able to do a diff or annotate direct from the IDE but not a great deal else. I don't think it's any substitute for using a separate standalone client such as SmartSVN or Versions.
You also have to jump through a number of hoops to get Xcode to work with SVN version 1.5 onwards, so that's something to be aware of before installing a standalone client. If in doubt, check out a sandbox first.
Here is one of the best tutorials to configure subversion in XCode - http://iphonedevelopment.blogspot.com/2009/03/version-control-is-your-friend.html
It also teaches even to create repository in local MAC.
if you want to work with svn through a gui interface then i suggest you use eclipse + subclipse plugin (which have more features and much more reliable and easy than svn on xcode)..
you will work in xcode as normal but you will use eclipse only as an svn client (by creating a general project in eclipse and make it points to your xcode project directory )
and here is a tutorial of how to install subclipse
A lot of people have problems using the build in svn client, especially to get a new project into svn and that it works.
I created a straight foreward tutorial on how to do this, along with a very well known pitfall (works for Xcode up till the latest version of xcode incl. Iphone 4 sdk)
http://www.sodeso.nl/?p=599
I myself looked up for some good resources and one of the best I've found is a quite recent video from the WWDC 2012 :
Sign in here if it's not already the case : https://developer.apple.com/videos/wwdc/2012/
Then there is a video called :Session 411 - Source Control Management in Xcode
It explains how to use version control both with GIT and Subversion. It's really nice !
Hope it helps!
As has been mentioned in many other answers, the svn client with Xcode is quite weak (and that is being kind).
Personally, I think that running Eclipse just to get access to a svn client is a bit heavy handed.
I would suggest two answers:
Use a dedicated svn client for the Mac (Versions and Cornerstone are both very good, albeit not free... there are free ones, such as svnX)
If you are not wildly comfortable with the terminal, you can script a couple of the key commands that you want to use and add them to your Xcode user scripts folder, then you can trigger them from a menu item of from a keystroke, just as if you were using the Xcode native client. There's a ton of examples on how to do this available via Google.
I came across these - no idea how well they work, but wanted to add some resources if I could:
http://www.macresearch.org/tutorial-introducing-xcode-30-organizer
http://developer.apple.com/tools/subversionxcode.html
With XCode4 you can perform almost all of your SCM tasks from within the IDE itself, this is a great step forward.
Here is a link to the official guide :
http://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/SCM/SCM.html#//apple_ref/doc/uid/TP40010215-CH7-SW26
Unfortunately you still have to use the Terminal command line to add a new project to SCM, this is also clearly documented in the link above.
What it does not tell you is that you also need to manually add ignore instructions to your SCM configuration otherwise you are going to end up with user settings and build outputs in your repositories. I am currently figuring out the list and I will update this answer once I have it finalised.
PS :
I know this question is quite old now but I have added this for those of you who arrive here looking for answers like I did.
PPS :
Terminal command line increases probability of human error, takes longer, is more complex and is less transparent to end users. Overall the omission of being able to add projects to SCM from within XCode is poor design, I expected better from Apple who are usually good at simplifying UI. For the command line fans out there you might feel L337 but try managing a team of programmers and being responsible for their code, command line is not your friend.
I like the status email sent by TFS's alerts mechanism when a build breaks.
However I would like to send such an email to the entire team and not rely on the team to subscribe to the alert...
Having a hard time producing a nice and detailed enough message by myself when overriding the "OnBuildBreak" and using the MSBuildCommunityTasks EMail task.
Is there a way to force a TFS alert to be sent to a list of emails?
Can you recommend of a way to send such status notifications?
You could try.
Brian the build bunny
:-)
The Team Build Tray Notification tool what is included in the TFS 2008 Power Tools is very useful for this.
See Buck Hodges' blog for screenshots and more information.
I don't want to dig up an old topic, but for those that stumble upon it two years late (like me), this is built into TFS 2010 now.
Set up an email alias for the team on the mail server, and enter this when subscribing to the mail.
Try the Team Foundation Server Event Subscription Tool.
This allows you to send emails to any address when any TFS event occurs.
Brian the Build bunny is nice but the Nabaztagtag WiFi Rabbit bunny is pretty expensive and is currently out of stock.
The Team Build Tray Notification that comes with TFS is ok, but:
It's damn slow and polling is not configurable
It's too easy to miss the build being broken for projects you care about
Doesn't support different actions for different projects (e.g. show a modal dialog for project #1, but just show a short tray alert for project #2)
Doesn't support different triggers for different people (e.g. show notifications for just me on project #1 or anyone on project #2)
No information on what broke the build (e.g. compiler error, unit test, integration test)
No audible notification if system's on mute
No last build times
So there's an open source project on Google Code that runs in the tray that's available on Google Code: http://code.google.com/p/siren-of-shame/. That project can work independently but it's designed to work with a USB Siren that is available for sale.
I generally like the TFS Build Status Tray by Rob Aquila. Be sure to get the 1.0.1 Beta, as this lets you easily specify the projects to watch using a bit of GUI and also has a notify icon that changes color, so you only need to open the actual build status list when the icon turns red. The 1.0 version had a fixed icon, and only notify toasts in the corner of your screen.
There is also a version of the same tool that is meant to be shown full screen on a wall mounted display for instance.
The July release of TFS 2008 PowerTools adds an "Alert Editor" to Team Explorer. Adding Alerts is a breeze. It has a query tool similar to the Query tool.
In my mind, a open source project named 'Web Deployment Projects' can do this. your can search for it.