|
Synergy 7.2 - can't get the mapping rules to work 100%. 1. The default rules ignore .o files and obj directory. We built .o files in a lib directory and added to the mapping_rules after INCLDUE ATUO RULES to override and Set Type of .o to 'library'. The admin did a DB refresh,and still Sync (from the GUI) does not show any .o files for the build manager's int prep project.
I can manually add a file of .o and set the type to 'library'. If I set the file to prodcut and recompile it, will a command line reconclie update the .o on an auto task (ie the builder doesn't need to provide an assigned task ID)?
2. It looks like the default rule is to ignore .md files. We build a lot of these and the Sync (GUI toolbar) shows all the .md files as conflicts.
How come the rules aren't doing what they say?
Thanks
|
|
|
Collaborating with ALM and Agile: An Interview with Karthik Ravindran
Video
Karthik Ravindran, Microsoft Senior Director - Visual Studio Product Management, discusses the evolution of ALM and agile and how each can reach its full potential when they are working together in an organization.
|
|
|
Exposing and Erasing Organizational Bias: An Interview with Keith Klain Keith Klain gives a glimpse at what he'll be discussing at his upcoming STARCANADA session, "Creating Dissonance: Overcoming Organizational Bias toward Software Testing." Learn the numerous benefits of discovering these biases before they do more damage than they've already done.
|
|
|
Information Technology Predictions for 2013 While 2013 may appear calmer compared to 2012 due in part to fewer “big” events scheduled this year, the information technology (IT) industry and profession advances forward. The IT industry, interestingly enough, shapes events in addition to being shaped by events around the world.
|
|
|
Estimating in Software Development: No Silver Bullets Allowed
Slideshow
What do poker, Greek oracles, an Italian mathematician from the Middle Ages, and the path of hurricanes have in common? Given the title of this presentation, chances are it has something to do with estimation, and you'll have to attend this session to get the full connection. Kent McDonald explores the challenges and realities of trying to estimate software-related knowledge work-analysis, testing, development, and the entire project effort. A major challenge is that there are no guaranteed ways to arrive at perfectly accurate estimates, which not surprisingly is why they are called estimates. Kent introduces and gives you a chance to practice quick and practical estimating techniques that will work in different situations-guesstimating, break it down and add it up, and planning poker.
|
Kent McDonald, Knowledge Bridge Partners
|
|
Massive Continuous Integration and Light-speed Iterations
Slideshow
Continuous integration (CI) has become a buzzword, with most engineering organizations claiming they've adopted the practice. However, the sad truth is that unreliable tests, long feedback loops, and poor configuration management block their efforts and minimize CI's potential benefits. Jesse Dowdle shares how AtTask radically redesigned its engineering pipeline and, through massive CI scaling, drove three days of testing to just minutes. Learn the pros and cons of different CI systems and how to integrate them with the cloud. Watch a live demo of AtTask's internal test and CI systems, which they’ve designed to make "Every commit a potential release candidate"-meaning that every commit is an iteration. Arm yourself with the talking points to sell massive CI to executives.
|
Jesse Dowdle, AtTask, Inc.
|
|
Creating Great User Experiences: Tips and Techniques
Slideshow
Many software people look at creating great user experiences as a black art, something to guess at and hope for the best. It doesn't have to be that way! Jennifer Fraser explores the key ingredients for great user experience (UX) designs and shares the techniques she employs early-and often-during development. Find out how Jennifer fosters communications with users and devs, and works pro-actively to ensure true collaboration among UX designers and the rest of the team. Whether your team employs a formal agile methodology or not, Jennifer asserts that you need an iterative and incremental approach for creating great UX experiences. She shares her toolkit of communication techniques-blue-sky brainstorming sessions, structured conversation, and more-to use with different personality types and describes which types may approach decisions objectively versus empathetically.
|
Jennifer Fraser, Macadamian
|
|
Back to the Basics: Principles for Constructing Quality Software
Slideshow
Using an analogy to the building codes followed by architects and contractors in the construction of buildings, Rick Spiewak explores the fundamental principles for developing and delivering high quality, mission-critical systems. Just as buildings are constructed using different materials and techniques, we use a variety of languages, methodologies, and tools to develop software. Although there is no formal "building code" for software, software projects should consider-and judiciously apply-the recognized "best" practices of static analysis, automated unit testing, code re-use, and peer reviews. Rick takes you on a deep dive into each of these techniques where you'll learn about their advantages, disadvantages, costs, challenges, and more.
|
Rick Spiewak, The MITRE Corporation
|
|
The Right Question for the Right Requirements
Slideshow
How often have you gone down the road of developing software almost to completion only to discover new requirements that require significant design and coding changes at the last minute? Requirements analysis is not just writing down what customers say they want. It's about digging down and discovering what they need. Without real analysis, our requirements often end up as poorly defined lists, anemic mock-ups, and incomplete or inconsistent models. Jack Jones spotlights one simple technique to discover these needs: Ask "why?" When the customer states a requirement, ask "why?" to delve down a level to discover their real problem, need, or opportunity. You may find you need to repeat "why?" a number of times. Join Jack to explore the very real consequences of not comprehending customer needs early in the process, and practice better communications techniques to avoid unnecessary requirements and scope changes.
|
Jack Jones, KMI
|
|
Danger! Danger! Your Mobile Applications Are Not Secure
Slideshow
A new breed of mobile devices with sophisticated processors and ample storage has given rise to sophisticated applications that move more and more data and business logic to devices. The result is significant and potentially dangerous security challenges, especially for location-aware mobile applications and those storing sensitive or valuable data on devices. To counter these risks, Johannes Ullrich introduces and demonstrates design strategies you can use to mitigate these risks and make applications safer and less vulnerable. Johannes illustrates design patterns to: co-validate data on both the client and server; authenticate transactions on the server; and store only authenticated and access-controlled data on the client. Learn to apply these solutions without losing access to powerful HTML5 JavaScript APIs such as those required for location-based mobile applications.
|
Johannes Ullrich, SANS Technology Institute
|